Coordinated delivery of dining experiences

ABSTRACT

According to one aspect, a method for executing a multi-restaurant order, may be provided; the method comprising: receiving a multi-restaurant order comprising requesting a plurality of order items associated with a plurality of restaurants from a customer; calculating a time to begin preparing a first order item associated with a first restaurant; calculating a time to begin preparing a second order item associated with a second restaurant; comparing the times; scheduling, based on the comparing, a first time to begin preparation of the first order item and a second time to begin preparation of the second order item; transmitting the first and second time to begin preparation to the first and second restaurant, respectively; generating a plurality of proposed pickup times, based on the scheduling, of the first order item and the second order item; and transmitting the plurality of proposed pickup times to a driver management module.

RELATED APPLICATION

This application is a Continuation-In-Part of U.S. application Ser. No.17/173,848 filed Feb. 11, 2021, which claims priority to U.S.Provisional Application No. 62/972,762 filed Feb. 11, 2020, which arehereby incorporated by reference herein in their entirety.

It is intended that the above-referenced application may be applicableto the concepts and embodiments disclosed herein, even if such conceptsand embodiments are disclosed in the referenced applications withdifferent limitations and configurations and described using differentexamples and terminology.

FIELD OF DISCLOSURE

The present disclosure relates to devices, systems, and methods forcoordinating the delivery of a dining experience to customers, forexample, through a food delivery service.

BACKGROUND OF THE DISCLOSURE

Generally, customers desiring particular order items must determineparticular restaurants that can prepare such order items, order saidorder items, and either pick up the order items or have them delivered.In some scenarios, a particular restaurant may only offer a portion ofthe desired order items, for example, an appetizer, while a secondrestaurant may offer a different portion, for example, an entrée. Inthese scenarios, the customer must pick up each order item individually,or have them delivered from multiple food delivery providers. Itfollows, that these order items may be at an unideal temperature whendelivered or picked up due to the multiple stops involved in completingacquisition from multiple restaurants or arrive at different moments.

Further still, groups of people, such as families or those residing thesame household, may have individuals that desire to order items fromdifferent restaurants, but plan to eat the order items at the same time.Conventional delivery solutions do not enable a multi-restaurant,multi-person group order comprised of a plurality of order items, allassociated with different restaurants and different individuals withinthe group, to be coordinated for timed delivery, through a single order.

Accordingly, there remains a need for coordinated preparation anddelivery of dining experiences that overcome these and other drawbacks.These and other needs are satisfied by the various aspects of thepresent disclosure.

BRIEF OVERVIEW OF THE DISCLOSURE

In accordance with the purposes of the disclosure, as embodied andbroadly described herein, the disclosure, in one aspect, relates tocoordinating the delivery of a dining experience to customers, forexample, through a food delivery service.

According to one aspect, a software-based operation and managementplatform is provided to manage certain preparation, pickup, and deliveryorders. The platform may be used by multiple restaurants, regardless oftheir facility location. Moreover, the platform may also be used bycommon kitchen facilities, as will be further detailed below.

The software can control various aspects related to the foodpreparation, timing, and scheduling of pickups and delivery. Thesoftware can also manage the same activities in regard to preparation,timing, scheduling of pickups of food providers outside of the building,in combination with restaurants in a common kitchen facility. Thesoftware can allow a customer to define a delivery time for amulti-restaurant order and schedule the activities of the restaurantsparticipating in the order, considering preparation and delivery/traffictime in the planning.

According to additional aspects, the scheduling will consider thepreparation time of each recipe and may include a database with thepreparation time per recipe per restaurant.

According to additional aspects, the scheduling will consider thedelivery and pickup delay/time of each recipe and may include a databasewith the delivery times and/or pickup times per restaurant.

According to additional aspects, the scheduling will consider trafficdelays, temperature increase/decrease based on travel time, weather, andother potential delays and impacts in delivering a desirable diningexperience.

According to additional aspects, digital marketing services andmonetization services may be provided to platform users to facilitategrowth of their business and geographical presence.

According to one aspect, a building (e.g., a warehouse-like facility)with many commercially operable kitchens may be provided. A “tenant” ofsuch a facility would be a food provider such as, for example, arestaurant or a virtual restaurant that desires to have a kitchen in thebuilding. As used herein, virtual restaurants can be defined asrestaurants with a brand that only sell through delivery, or do not havea physical establishment for customers to dine within.

It is noted that expanding to additional locations and, thus, additionalgeographic territories, enables the expansion of the restaurant'sprospective customer base. By renting a kitchen in a facility consistentwith aspects of the present disclosure, a restaurant can expand itsterritory without committing additional resources beyond the kitchen andcook/s, thereby saving on dine-in resources such as staff, tables,supplies, service, and other patron servicing requirements. Thisfacilitates the restaurant to gain market share on purely delivery andcarry-out customers, leading to higher margins on their products. By thetransient nature of a kitchen rental, the restaurant may obtain the datait needs to decide if the new location warrants an expansion of itsdine-in segment.

It is further anticipated that aspects of the disclosure will benefitconsumers as well as restaurants. For instance, a consumer may desire an‘appetizer’ from a first restaurant, but an ‘entree’ from a secondrestaurant. There is no current solution that would enable the consumerto receive both items, from different restaurants, at the same time,using the same delivery service, within a reasonable time such that thefood, when received, remains at a reasonable temperature forconsumption. Additionally, the consumer could schedule the delivery timeof its multi-restaurant order, and aspects disclosed herein willorganize the preparation of the food at the restaurants providing theorder, considering preparation and delivery times, including traffic.

Moreover, there is no current solution that enables a restaurant tosynchronously time the preparation of their food in conjunction with amulti-stop route by a decentralized driver. Thus, management softwareaspects of the present disclosure may be comprised of componentsincluding: 1) consumer-facing, multi-restaurant piecemeal delivery; and,2) management of decentralized food preparation from multiplerestaurants as applied to the same order. It should be noted that, incertain embodiments, the multi-point delivery may all be from the samewarehouse comprising different kitchens.

Moreover, by enabling such piecemeal delivered from a plurality of foodproviders, this not only benefits the customer, but the food providermay stand to increase sales. The restaurant can increase sales—and notjust by geographic expansion alone, but by enabling customers to onlyorder their favorite items from their favorite restaurant, whereasbefore they would face an ‘all or nothing’ decision.

Generally, according to aspects of the disclosure, a method of deliveryof a dining experience can include presenting a menu or multiple menusfrom different restaurants to a customer, receiving a request from thecustomer including at least one order item, and coordinating completedorder pickup from one or more restaurants by a delivery provider suchthat a consistent and pleasing dining experience is provided to thecustomer.

The method of delivery of the dining experience can also includeassociating traffic data, weather data, ranking data, and/or otherapplicable data to match delivery providers with restaurants such thatthe consistent and pleasing dining experience is facilitated. Deliveryproviders may be affiliated with the food provider (e.g., therestaurant) by way of, for example, but not limited to, employment,contracting, or third-party selection through the platform of thepresent disclosure.

In still further aspects, the disclosure also relates to devices andsystems utilizing or facilitating the methods described herein.

Aspects of the disclosure may enable a multi-restaurant, multi-persongroup order comprised of a plurality of order items, all associated withdifferent restaurants and different individuals within the group, to becoordinated for timed delivery, through a single order. Advantages mayinclude, but not be limited to, the timing of multiple order items, frommultiple sources, to multiple individuals, to ensure that each orderitem is in optimal condition upon arrival, as well as timed to arriverelatively with the other order items in the order. In this way, in onenon-limiting example, family members or co-workers desiring to eattogether, but with preferences on order items at different restaurants,may enjoy a coordinated delivery of the order items such that the orderitems may be received at relatively the same time.

Providing the aforementioned aspects may include the proper timing offood preparation of restaurants, as well as the timed dispatch of one ormore delivery providers to pick up, route, and delivery the order itemsat relatively the same time, in optimal condition. Consolidating ordersfrom multiple individuals and a plurality of restaurants may provide aneconomical advantage to a user of the present disclosure. The user mayonly be required to pay one fee for the entire order in the presentdisclosure, rather than separate fees from each restaurant and/ordeliver service they may have otherwise ordered from.

Additional aspects of the disclosure will be set forth in part in thedescription which follows, and in part will be obvious from thedescription, or can be learned by practice of the disclosure. Theadvantages of the disclosure will be realized and attained by means ofthe elements and combinations particularly pointed out in the appendedclaims. It is to be understood that both the foregoing generaldescription and the following detailed description are exemplary andexplanatory only and are not restrictive of the disclosure, as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of this specification, illustrate several aspects of the disclosureand together with the description, serve to explain the principles ofthe disclosure.

FIG. 1 is an overview of a system or platform 100, according to anexemplary embodiment of the present disclosure;

FIG. 2 illustrates a flowchart of a method 200, according to anembodiment of the present disclosure;

FIG. 3 illustrates a flowchart of a method 300, according to anembodiment of the present disclosure;

FIG. 4 illustrates a flowchart of a method 400, according to anembodiment of the present disclosure;

FIG. 5 is a flowchart of a method 500, according to an exemplaryembodiment of the present disclosure;

FIG. 6 illustrates a computing device, according to an exemplaryembodiment of the present disclosure;

FIG. 7 illustrates a flow chart of a user launching platform 100according to an embodiment of the present disclosure;

FIG. 8 illustrates a flow chart for a user profile module according toan embodiment of the present disclosure;

FIG. 9 illustrates a flow chart for a sharing option according to anembodiment of the present disclosure;

FIG. 10A illustrates a flow chart for launching platform 100 accordingto an embodiment of the present disclosure;

FIG. 10B illustrates a flow chart for adding at least one food item tothe multi-restaurant order according to an embodiment of the presentdisclosure;

FIG. 11 illustrates a flow chart for a user completing amulti-restaurant order according to an embodiment of the presentdisclosure;

FIG. 12 illustrates a flow chart for a favorites module according to anembodiment of the present disclosure;

FIG. 13 illustrates a flow chart for a delivery provider accessingplatform 100;

FIG. 14A illustrates a flow chart coordinating and delivering themulti-restaurant order once the multi-restaurant order has beenrequested and/or confirmed according to an embodiment of the presentdisclosure;

FIG. 14B illustrates a flow chart coordinating and delivering themulti-restaurant order once the multi-restaurant order has beenrequested and/or confirmed according to an embodiment of the presentdisclosure;

FIG. 14C illustrates a flow chart coordinating and delivering themulti-restaurant order once the multi-restaurant order has beenrequested and/or confirmed according to an embodiment of the presentdisclosure;

FIG. 15A illustrates a flow chart in which the delivery provider acceptsat least one product and/or food item of the multi-restaurant request;

FIG. 15B illustrates a flow chart in which the delivery provider acceptsat least one product and/or food item of the multi-restaurant request;

FIG. 16A illustrates a flow chart for a restaurant launching platform100;

FIG. 16B illustrates a flow chart for a restaurant launching platform100;

FIG. 17 illustrates a flow chart for additional options of the userafter the confirmation of a multi-restaurant order;

FIG. 18 illustrates a flow chart of communication between a mobileclient of platform 100, the back end of platform 100, a payment gatewayof platform 100, and/or a community driven map service of platform 100according to an embodiment of the present disclosure;

FIG. 19 illustrates a method 2500 incorporating elements of methods200-500;

FIG. 20 illustrates a context diagram of payment and funding flow usingplatform 100 according to an embodiment of the present disclosure; and

FIG. 21 illustrates a business flow diagram of platform 100 according toan embodiment of the present disclosure.

DETAILED DESCRIPTION OF THE DISCLOSURE

As a preliminary matter, it will readily be understood by one havingordinary skill in the relevant art that the present disclosure has broadutility and application. As should be understood, any embodiment mayincorporate only one or a plurality of the above-disclosed aspects ofthe disclosure and may further incorporate only one or a plurality ofthe above-disclosed features. Furthermore, any embodiment discussed andidentified as being “preferred” is considered to be part of a best modecontemplated for carrying out the embodiments of the present disclosure.Other embodiments also may be discussed for additional illustrativepurposes in providing a full and enabling disclosure. Moreover, manyembodiments, such as adaptations, variations, modifications, andequivalent arrangements, will be implicitly disclosed by the embodimentsdescribed herein and fall within the scope of the present disclosure.

Accordingly, while embodiments are described herein in detail inrelation to one or more embodiments, it is to be understood that thisdisclosure is illustrative and exemplary of the present disclosure andare made merely for the purposes of providing a full and enablingdisclosure. The detailed disclosure herein of one or more embodiments isnot intended, nor is to be construed, to limit the scope of patentprotection afforded in any claim of a patent issuing here from, whichscope is to be defined by the claims and the equivalents thereof. It isnot intended that the scope of patent protection be defined by readinginto any claim a limitation found herein that does not explicitly appearin the claim itself.

Thus, for example, any sequence(s) and/or temporal order of steps ofvarious processes or methods that are described herein are illustrativeand not restrictive. Accordingly, it should be understood that, althoughsteps of various processes or methods may be shown and described asbeing in a sequence or temporal order, the steps of any such processesor methods are not limited to being carried out in any particularsequence or order, absent an indication otherwise. Indeed, the steps insuch processes or methods generally may be carried out in variousdifferent sequences and orders while still falling within the scope ofthe present invention. Accordingly, it is intended that the scope ofpatent protection is to be defined by the issued claim(s) rather thanthe description set forth herein.

Additionally, it is important to note that each term used herein refersto that which an ordinary artisan would understand such term to meanbased on the contextual use of such term herein. To the extent that themeaning of a term used herein—as understood by the ordinary artisanbased on the contextual use of such term—differs in any way from anyparticular dictionary definition of such term, it is intended that themeaning of the term as understood by the ordinary artisan shouldprevail.

Regarding applicability of 35 U.S.C. § 112, ¶6, no claim element isintended to be read in accordance with this statutory provision unlessthe explicit phrase “means for” or “step for” is actually used in suchclaim element, whereupon this statutory provision is intended to applyin the interpretation of such claim element.

Furthermore, it is important to note that, as used herein, “a” and “an”each generally denotes “at least one,” but does not exclude a pluralityunless the contextual use dictates otherwise. When used herein to join alist of items, “or” denotes “at least one of the items,” but does notexclude a plurality of items of the list. Finally, when used herein tojoin a list of items, “and” denotes “all of the items of the list.”

The following detailed description refers to the accompanying drawings.Wherever possible, the same reference numbers are used in the drawingsand the following description to refer to the same or similar elements.While many embodiments of the disclosure may be described,modifications, adaptations, and other implementations are possible. Forexample, substitutions, additions, or modifications may be made to theelements illustrated in the drawings, and the methods described hereinmay be modified by substituting, reordering, or adding stages to thedisclosed methods. Accordingly, the following detailed description doesnot limit the disclosure. Instead, the proper scope of the disclosure isdefined by the appended claims. The present disclosure contains headers.It should be understood that these headers are used as references andare not to be construed as limiting upon the subjected matter disclosedunder the header.

The present disclosure includes many aspects and features. Moreover,while many aspects and features relate to, and are described in, thecontext of multi-restaurant, multi-person orders, embodiments of thepresent disclosure are not limited to use only in this context, and maybe applicable to any circumstances in which similar methods of logisticsand operational management are employed.

Platform Overview

As briefly described above, the present disclosure relates, in variousaspects, to methods, devices, and systems for coordinated delivery ofdining experiences to customers. Turning now to the figures, severalaspects of the present disclosure are described in detail. It is notedthat the drawings are not to scale, and are not exhaustive of allaspects of the present disclosure.

In a first aspect of the present disclosure, embodiments provide for amulti-kitchen, multi-brand and/or multi-restaurant (collectivelyreferred to as multi-restaurant) ordering, management, and deliverylogistics platform. As will be detailed, embodiments herein provide fora consumer interface for placing a multi-restaurant ordering softwareapplication interface. Furthermore, embodiments herein provide for akitchen-management platform that orchestrates the preparation sequenceand timing of various orders at each kitchen relevant to amulti-restaurant order placed via the consumer interface. Further still,embodiments of the present disclosure provide for a delivery managementplatform that coordinates a decentralized network of delivery vehicles,as such may be contemplated to be human-operated or autonomous delivery,for the proper dispatch, routing, and overall timing in the fulfillmentof the multi-restaurant order. Said embodiments may be integrated intovarious decentralized ordering and delivery platforms, includingintegration with ride-share service providers. In this way, for the sameorder, multiple restaurants as well as multiple delivery providers maybe used to deliver the same order comprised of multiple order items froma different location. Accordingly, each restaurant, regardless of itsplatform, and each delivery provider, regardless of its platform, may beenabled and/or configured to communicate with the centralizedcoordinating platform of the present disclosure, thereby leveragingmultiple sources and delivery assets in facilitating a single order.Thus, a first restaurant may be different in technical implementationfrom a second restaurant, but still in bi-directional communication withthe central platform for the purposes of unified order fulfillment.Similarly, a first delivery unit may be from a first delivery network,while a second delivery unit may be from a second delivery network, allin bi-directional communication with the central platform for thepurposes of unified order fulfillment.

Accordingly, in the first aspect, embodiments of the present disclosureenable multi-restaurant orders to be placed, received, and processedthrough a consumer facing platform. In further embodiments, as will bedetailed with regard to additional aspects, multiple users may beenabled to aggregate their ordered order items from multi-restaurantsinto a single orchestrated order for coordinated fulfillment.

Subsequently queued and processed in a kitchen management platform forthe orchestration of multi-kitchens and coordination of timing withineach kitchen. By way of non-limiting examples, the platform may takeinto consideration the recipe parameters, the location of the kitchen,the preparation time, the serving parameters, and various otherconsideration relating to the timely and proper (e.g., temperature)delivery of the multi-restaurant order, in view of the relatedparameters for the other kitchens pertaining to the samemulti-restaurant order. In this way, the platform may instruct when thekitchen should commence preparation of an order item with that kitchen.

Still referencing the first aspect, the delivery management platform maybe enabled to dispatch drivers in a decentralized network of drivers. Itshould be understood that, although the terms ‘driver’ is used, anymeans by which the transportation of the multi-restaurant order to thecustomer may be employed, including, but not limited to, drone-baseddelivery. In additional aspects, one or more drivers may be dispatched,and at varying times, to ensure the timely and proper fulfillment of themulti-restaurant and group orders.

The various embodiments herein may be managed in a centralized computingplatform. That is, the consumer interface, the kitchen management, andthe delivery management platforms may be management by a larger,centralized platform for coordinating the multiple aspects describedherein. Moreover, the various platforms may be, in part or in whole,integrated with other platforms such as pre-existing consumerinterfaces, pre-existing kitchen management interfaces, and pre-existingdelivery management solutions. In this way, the various embodimentsherein may be codified as an API and/or SDK for integration with varioustechnical platforms. Together, the platform may provide for theoptimized fulfillment of multi-restaurant orders for one or moreconsumers, by way of an orchestrated process flow that is “transparent”(e.g., not disruptive of ordinary operations) to any single partyinvolved in the process.

In a second aspect of the present disclosure, methods, systems, andcomputer-readable media may be provided to solve one or more problems inconventional solutions. The first problem relates to the facilitation ofgroup orders. Conventionally, facilitating group orders is cumbersomeand difficult. A primary user may be responsible for facilitating theirorder on a single account. This process becomes exponentially morecomplicated the more people are involved in the order and when differentpeople prefer to order items from different restaurants. Here, theplacing of multiple orders, from multiple restaurants, on behalf ofmultiple people is technically constrained by current softwaresolutions. Finally, the process of aggregating payment details andinformation, whether through the ordering platform, or outside of theordering platform, is further technically constrained by the lack ofinterface for obtaining fee splits for multi-person, multi-restaurantgroup orders. It should be understood that the various embodiments mayrefer to multi-person orders may also apply to single-person orders.

It is noted that “order items,” “items” and/or “order items” may beinterchangeable with the following: at least one product, at least onefood product, at least one restaurant item, at least one portion of anorder item, and at least one portion of a product.

To address these problems, embodiments of the present disclosure enablea multi-person, multi-device aggregation of a single, multi-restaurantorder. In this way, embodiments of the present disclosure may be used toconstruct a unified multi-restaurant order, from one or morerestaurants, with one or split payments, in a single process, using onor more devices to input, track, and transact the parameters of themulti-restaurant order. In some embodiments, a unifying multi-restaurantorder may be constructed through a platform consistent with embodimentsherein. Here, different users may access the same platform and input theparameters of their portion of the multi-restaurant order and paymentinformation. In turn, the order items from the various users may beaggregated and placed as a single order into the platform.

Still, consistent with embodiments of the present disclosure, multipledesperate order items may be tagged and aggregated to form a unifyingmulti-restaurant order. For example, a first user may place a firstorder for a first order item at a first restaurant and complete thefirst order, while a second user may place a second order for a secondorder item at a second restaurant and complete the second order. Theplurality of orders may have been placed on the same or differentplatforms. In turn, various methods and systems may be employed topropose that the separate orders may be aggregated to form a unifyingmulti-restaurant order, managed for optimal delivery. Such proposal maybe triggered based on the plurality of orders being received, atapproximately the same time, for delivery to the same address. Thisproblem may have been solved by some of the prior art findings wediscovered. Thus, any one of the aforementioned elements may only form acomponent of an independent patent claim.

In a third aspect of the various embodiments presented herein,multi-restaurant orders for one or more consumers may be timed to arriveat a desired time or interval of times. This may be achieved, at leastin part, through the timed dispatch of delivery drivers. For instance,embodiments of the present disclosure may provide for the incrementaldispatch of delivery drivers as needed to fulfill a desired coordinateddelivery of the plurality of order items. Here, the various componentsof the first and second aspects mentioned above and detailed herein, todeliver the food for multiple restaurants.

The platform may be configured schedule multiple delivery providers ifrequired, in order for order items from different restaurants to arriveat the same time. As one example, the platform may set a constraint ofthirty minutes for a delivery. That is, the platform will optimize theorder items such that a hot dish would not spend more than thirtyminutes in the vehicle until delivery, therefore the multi-restaurantorder may require more than one driver for pickup. For instance, when afour-restaurant order fulfilled by only one driver would take over anhour to fulfill, the platform would dispatch additional drivers tomaintain a thirty-minute maximum between the pickup of the hot dishuntil the moment of delivery.

Consistent with a fourth aspect of the present disclosure, embodimentsof the present disclosure may provide a recommendation engine. Therecommendation engine may assist a user in determining forming amulti-restaurant order through the consumer interface. Therecommendation engine may employ various parameters in determining itsrecommendation. The parameters may comprise, but not be limited to, forexample, a history of consumption, a characteristic of the user's orderitems (e.g., organic foods, low fat foods, low carb foods), an aspect ofthe user's diet (e.g., keto-friendly foods, gluten-free foods, and thelike), and aspect of the ingredients within the order items that theuser prefers (e.g., the user prefers recipes with cilantro, curry, orother commonly occurring ingredients), geographical origin, and otherparameters. Further still, the recommendation engine may be configuredto group certain restaurants and their items together for presentationto the user. In some embodiments, the idea of restaurant-based menus maybe eliminated. Rather, a listing of items and/or corresponding brandsmay be presented to the user based on their preference. In this way, theorigination of the order may not be relevant to the user, as they canplace a multi-restaurant order through the embodiments herein.

Accordingly, various embodiments may provide a multi-restaurant,multi-person group order comprised of a plurality of order items, allassociated with different restaurants and different individuals withinthe group, to be coordinated for timed delivery, through a single order.Such order may be facilitated through a consumer interface, a kitchenmanagement platform, and a delivery and dispatch platform, all workingtogether to provide for the present solution. The consumer interface maybe configured to aggregate order items, for a plurality of individualsand a plurality of sources, into a unified order, and facilitate eithersingle or split payments. The kitchen interface may be configured tocoordinate the appropriate timing in the preparation of the order itemsin accordance with a target delivery time, across a plurality ofkitchens, having taken into consideration, by way of non-limitingexample, internal parameters (e.g., recipe, kitchen backlog, etc.) andexternal parameters (route, other kitchens in the order, deliveryproviders, etc.). The kitchen management platform may further indicatedelays or changes in the order preparation. The delivery interface maybe configured to route and dispatch, incrementally, as many deliveryproviders as necessary to fulfill the delivery of the ordered itemswithin a given parameter (e.g., temperature), a threshold period oftime, based on internal parameters (e.g., the food item parameters) andother parameters (e.g., traffic), and other factors, such that themultiple-drivers may deliver the items at relatively the same time.

Platform Architecture

FIG. 1 is an overview of a system or platform 100, according to anembodiment of the present disclosure. Platform 100 may, at any module,stage, and/or process comprise a User Interface (“UI”). Further,platform 100 may provide a set of instructions used to perform variousfunctions such as, for example, guiding and/or directing a user ofplatform 100 in response to the user's actions and/or selections whileusing platform 100.

As illustrated, platform 100 includes an optional warehouse facility 102where a plurality of restaurants 101 may be organized and situated foroperation and preparation for food and recipes. As noted, the warehouseconfiguration 102 may be optional, or may be in combination withexternal restaurant facilities. Accordingly, the restaurants 101 may beexternal to a warehouse, internal to warehouse, or in combinationinternal and external to a warehouse.

By way of non-limiting example, platform 100 may be hosted on, forexample, a cloud computing service. In some embodiments, the platform100 may be hosted on a computing device 600. A user may access platform100 through a software application and/or hardware device. The softwareapplication may be embodied as, for example, but not be limited to, awebsite, a web application, a desktop application, and a mobileapplication compatible with the computing device 600.

Still consistent with embodiments of the present disclosure, platform100 may be, for example, but not limited to, a software development kit(SDK)/application programming interface (API). The SDK/API may be usedby third parties to integrate some or all of the functions disclosedherein. Furthermore, the SDK/API may allow for the customization of someor all of the functions disclosed herein, to meet the needs of thirdparties implementing platform 100.

In yet further embodiments of the present disclosure, platform 100 mayimplement an SDK/API to integrate with third-party solutions. Forexample, and as mentioned below, platform 100 may integrate with adelivery provider's management platform to manage the delivery aspectsdisclosed herein. In yet another example, platform 100 may integratewith an inventory management platform used by, for example, restaurants.It should be understood that the SDK/API integrations may enableadministers to selectively use and deploy various functions and featuresherein, in any customized integration with existing third-partyplatforms.

The platform 100 may include a network 110 to facilitate communicationbetween the restaurants 101, between the restaurants 101 and a deliveryprovider 112, between the restaurants 101 and customers 104, and/orbetween the delivery provider 112 and customers 104.

In accordance with various embodiments disclosed herein, deliveryprovider 112 may be affiliated with the food provider (e.g., therestaurant 101) by way of, for example, but not limited to, employment,contracting, or third-party selection through platform 100 of thepresent disclosure. The selection may be provided by, either one of therestaurants 101 or the customer 104. Furthermore, these sections may befacilitated through platform 100. Further still, in some embodiments,the delivery provider 112 may comprise a delivery management platformthat is in bi-directional communication with platform 100. In turn, thedelivery management platform and platform 100 may share data,computer-instructions, and any other aspect to inform, commission,manage, or otherwise track the delivery status of the multi-restaurantorder received by platform on customer 104.

Generally, the customers 104 may place a multi-restaurant request 106comprising one or more order items or recipes associated with therestaurants 101. The multi-restaurant request 106 may also be a singlerestaurant request in some embodiments.

The multi-restaurant request 106 may be received and processed by adelivery organizer 108. The delivery organizer 108 may be a softwarecomponent or a plurality of software components configured to executecomputer-readable instructions associated with one or more of methods200, 300, 400, and/or 500, which are described in more detail herein. Insome embodiments, delivery organizer 108 may be configured to identify atime latency to begin a new order item preparation for each of theplurality of restaurants. In further embodiments, delivery organizer 108may be configured to compare a plurality of predetermined preparationtimes of the one or more order items associated with the plurality ofrestaurants.

The delivery organizer 108 may be configured to process themulti-restaurant request 106 such that particular order items areordered from particular restaurants 101, such that payment to therestaurants are effectively distributed, such that delivery provider 112is effectively coordinated to facilitate delivery to customers 104, andsuch that payment to the delivery provider is effectively distributed.The delivery organizer 108 may use a web application, mobileapplication, or other interface to receive payment and requests from thecustomers 104.

Upon processing of the multi-restaurant request 106, the deliveryorganizer may distribute a series of processed requests 107 to eachassociated restaurant 101. Furthermore, the delivery organizer 108 maydistribute the multi-restaurant request to the delivery provider 112.The processed requests 107 may include data relating to preparationtimes for each order item in the request 107, as well as recommendedfood preparation start times, estimated pickup times of the deliveryprovider 112, and other related data. Thus, it is anticipated to bewithin the scope of the present disclosure that platform 100 may provideinstructions to, by way of non-limiting example, kitchen personnel.

In various embodiments, preparation times may be a data point availablefor each order item in the request 107. The data points may be providedby, for example, restaurant 101. For instance, during an on-boardingaspect of the restaurant's adoption of platform 100, or at any otherpoint in time, preparation times for each order item may be received byplatform 100. While, in other embodiments, the datapoints may beascertained from various other databases.

It is noted, that according to some embodiments, the processed requests107 may be provided to the restaurants 101 by the delivery provider 112.According to other embodiments, a portion of the processed requests 107may be provided by the delivery organizer 108, while an additionalportion may be provided by the delivery provider 112.

Responsive to receiving a request 107, the restaurants 101 may beginpreparation of each associated order item or recipe such that theanticipated pickup times are met. According to some embodiments, theanticipated pickup times may be based on a window or sliding scale oftime based on external factors, such as traffic, weather, and aspects ofthe recipe, including cooldown time (for hot recipes), heat up time (forcold or room temperature recipes such as salads, desserts, etc.),desired temperature at delivery, and other aspects. Furthermore, in someembodiments, a delivery driver profile may be provided. Said profile mayinclude data, such as, but not limited to, various aspects of thedelivery (e.g., thermal containers, chaffing tools, or coolers), thatwould factor into the delivery time calculation for ensuring timelydelivery of a particular recipe.

Each order item prepared may be organized by the restaurants 101 includeindividual order item portions 114. The individual order item portions114 may be collected by the delivery provider 112 and assembled intocompleted order item 116. The completed order item 116 may be stowed bythe delivery provider for delivery to the customers 104.

According to some embodiments, the delivery provider 112 may stow all ora portion of the completed order item 116 into specialized temperaturecontrol apparatuses for maintaining a desirable temperature. Upondelivery, the completed order item 116 may be at a desirable temperaturethereby ensuring a pleasing dining experience to the customers 104 ascompared to conventional delivery services.

It is noted that the coordination of the delivery and payment to therestaurants 101 and delivery provider 112 may vary in many ways.Hereinafter, particular details related to methods of coordinatingdelivery of a dining experience are presented in detail.

FIG. 7 illustrates a flow chart of a user launching system or platform100. Upon launching platform 100 at step 700, the user may be forwardedto a welcome screen and/or page 702. Welcome screen and/or page 702 maycomprise a prompt 704 to choose whether the user has an account or not.

Upon choosing that the user does have an account, the platform maydirect a user to a user login module 706 (alternatively: screen,display, and/or page). The user login module may comprise a plurality ofidentification criteria. The plurality of identification criteria maycomprise at least one of the plurality of user input requests. Theplurality of identification criteria may be used to prompt the user toenter at least one input to securely log in. Upon logging in and/or alogin confirmation, the platform may prompt the user to provide acurrent address in step 708. The current address may utilize a system toverify the validity of the address. Upon confirmation of the validity ofthe current address, the user may be directed to a home screen 710. HomeScreen 710 may provide a default address in step 712.

Upon choosing that the user does not have an account, the platform maydirect the user to an account creation interface and/or registrationpage 714. In some embodiments, the account creation interface maycomprise a plurality of user input requests. The plurality of user inputrequests may comprise at least one of the following: a name, a biometricidentification, a username, a user image, an age, a location, a date ofbirth, an email address, a password, a 2-step verification, an identityverification, a human verification, and an identification card scan. Insome embodiments, the plurality of user input requests may beautomatically filled via approval of at least one third-party platform.The plurality of user input requests may be used for creating a userprofile. In further embodiments, the account creation interface maycomprise a questionnaire. The questionnaire may be used to assist inassociating a user with a plurality of recommended restaurants.

Upon the creation of the account, a confirmation display 716 may beprovided. The confirmation display may be used as a result of the usersuccessfully completing the plurality of inputs and/or thequestionnaire. In some embodiments, the confirmation display may causeplatform 100 to send a confirmation link. The confirmation link may beprovided via email, text message, and/or any other notificationpreviously mentioned. The confirmation link may be used to associate theemail address to the user. The confirmation link may be further used toverify identification of the user.

Upon the confirmation and/or verification, the platform may direct theuser to home screen 710.

The home screen may provide a user access to at least one of thefollowing:

a) a user profile module 718;

b) a sharing option 720;

c) a favorites module 722;

d) a listing of available restaurants 724;

e) a cuisine-type filtering option 726;

f) an order module 728; and

g) an order tracking module 730.

User profile module 718, as illustrated in FIG. 8, may comprise aplurality of user information 732. Plurality of user information 732 maybe used to store, access, display, and/or modify the informationprovided from the plurality of user input requests and/or informationcomprised in the user login module.

User profile module 718 may provide an editing option 734 for personaluser information 732.

User profile module 718 may further provide a payment methods list 736.

Payment methods list 736 may comprise a new payment option 738. The newpayment option may prompt a user to fill out a virtual payment form 740which, upon completion, adds the new payment to payment methods list736.

User profile module 718 may further provide an orders list 742. Orderlist 742 may comprise order details 752 of a current multi-restaurantorder and/or details of previous multi-restaurant orders.

The user profile module my further provide an address list 744. Theaddress list may comprise a new address option 746. New address option746 may prompt a user to fill out a virtual address form 748 which, uponcompletion, adds the new address to address list 744.

User profile module 718 may further provide a help menu 750. Help menu750 may comprise a plurality of contact information 754. Plurality ofcontact information 754 may comprise a means to contact platform 100associates, the plurality of restaurants, and/or those associated withthe delivery of the plurality of order items. The means to contact maycomprise a communication virtual fillable form and/or document 756. Uponcompleting a communication virtual fillable form and/or document 756,the user may receive a confirmation notification 760. Help menu 750 mayfurther comprise a Frequently Asked Questions (“FAQ”) page 758. FAQ page758 may comprise a list of FAQs 762 relating to platform 100.

The sharing option 720, as illustrated in FIG. 9, may provide the userwith a share order selection 764. Share order selection 764 may compriseaccess to a contact list 766 of the user. Contact list 766 may comprisecontact information of a plurality of other users associated with theuser, and/or contact information comprised in a device of the user.Sharing option 720 may further allow the user to request and/orcontribute, as shown in 768, a selected amount of money to themulti-restaurant request and/or multi-restaurant order. Sharing option720 may be further used to invite at least one other user to join themulti-restaurant order.

Inviting other users to join the multi-restaurant order, as illustratedin FIG. 10A, may be sent via a plurality of notifications types. It isnoted that the plurality of notification types may be used at any stageand/or process of platform 100. The plurality of notification types maycomprise at least one push notification 1000. Push notification 1000 maybe used to display a notification as a text message sent to at least oneother user. In further embodiments, the plurality of notification typesmay comprise a banner. The banner may be used display a notification fora short time on the screen and disappear after. In yet furtherembodiments, the plurality of notification types may comprise an in-appalert. The in-app alert may be used to display a notification via pop upwindow on the platform and require action from the user to open or closethe in-app alert. In still further embodiments, the plurality ofnotification types may comprise a badge. The badge may be used todisplay a notification via small circles located on the corner of theplatform icon. In yet still further embodiments, the plurality ofnotification types may comprise an audible alert. The audible alert maybe used to inform the at least one other user of a notification.

The plurality of notifications may comprise a link and/or hyperlink.Selecting the link and/or hyperlink, as illustrated at stage 1002 mayprompt platform 100 to launch and/or be activated on the device of theat least one user. Upon the platform launching via the at least one userselecting at least one of the notification types, the user may bedirected to a welcome screen and/or page 1004. Welcome screen and/orpage 1004 may comprise an invitation message 1006. Invitation message1006 may be a customized message from the user and/or a prepopulatedmessage. Welcome screen and/or page 1004 may further comprise a joinorder option 1008 to join the multi-restaurant order.

Upon joining the order, the user (may include the at least one user andany other users joining the order), as illustrated in FIG. 10B, may bepresented with cuisine-type filtering option 726. Upon choosing one ofthe plurality of cuisines, a plurality of restaurants, specific to theselected cuisine may be presented as illustrated in 1010. Upon selectinga restaurant, a menu 1012 of a restaurant may be presented to the user.Upon choosing at least one product and/or order item from the menu, theat least one product and/or order item detail 1014 may be presented tothe user. Platform 100 may allow the user to select various optionsand/or customizations 1016 for the product and/or order item. The usermay then use an add to order option 1020 to select the at least oneproduct and/or order item to be added to the multi-restaurant order.

The user may alternatively, upon joining the multi-restaurant order,view a listing of available restaurants 724 without being filtered bycuisine type, as illustrated in FIG. 10B. Upon selecting a restaurant,menu 1012 of the restaurant may be presented to the user. Upon choosingat least one product and/or order item from menu 1012, the at least oneproduct and/or order item detail 1014 may be presented to the user.Platform 100 may allow the user to select various options and/orcustomizations 1016 for the product and/or order item. The user may thenuse an add to order option 1020 to select the at least one productand/or order item to be added to the multi-restaurant order.

The selected products and/or food options may populate on order module728, as illustrated in FIG. 11. Order module 728 may comprise an orderdetail module 1100 wherein the selected products and/or order items areaggregated, itemized, and/or displayed. Order detail module 1100 maycomprise a checkout option 1102. Order detail module 1100 may furthercomprise and edit/delete option 1004. Edit/delete option 1004 may allowthe user to add and/or delete selected products and/or order items fromthe multi-restaurant order. Order module 728 may be embodied as, forexample, a virtual shopping cart. Upon concluding the selection of thedesired products and/or order items, a checkout option 1102 may beselected. Upon selecting checkout option 1102, platform 100 may thendirect the user to a checkout module 1108. Checkout module 1108 and/ororder module 728 may allow for the time preference of delivery of eachof the products and/or order items.

The favorites module 722, as illustrated in FIG. 12, may comprise afavorites list 1200 of bookmarked and/or favorited order items,restaurants, and/or multi-restaurant orders. Upon the selection of afavorited multi-restaurant order, the user may modify themulti-restaurant order prior to proceeding to checkout module 1108.

Checkout module 1108 as illustrated in FIG. 11, may comprise profileinformation of each user associated with the multi-restaurant order suchas, for example, delivery address 704. The checkout module, prior toconfirming the multi-restaurant order, may request a confirmation,update, and/or selection of the delivery address 744. The checkoutmodule may further comprise a request at least one delivery instruction1100. At least one delivery instruction 1110 may comprise apredetermined selection of delivery instructions, and/or a text field1112 for customized instructions.

Checkout module 1108 may further comprise a request for a payment typeand/or preference (“Payment Methods List”) 1114 of the user. Therequested payment type, method, and/or preference may comprise at leastone previously entered and/or stored payment type and/or method of theuser. The user, as illustrated in 1118, may change the payment typeand/or method of the user. The requested payment type, method, and/orpreference may further comprise a new, previously not stored paymenttype and/or method 1116 of the user.

Checkout module 1108 may further comprise a share payment option 1120.Share payment option 1120 may provide a user the ability to prompt otherusers to provide a portion of the monetary amount due. Upon selectingshare payment option 1120, platform 100 may then access contact list 766of the user and/or the contact information of those participating in themulti-restaurant order. Selecting share payment option 1120 may furtherallow a user to manually input a new contact 1122. New contact 1122 mayor may not be another user of platform 100. Once each user associatedwith the multi-restaurant order is added to the multi-restaurant order,the user may choose to divide the sharing of payment by percent and/orby itemized products and/or order items associated with themulti-restaurant order, as illustrated by 1124.

Checkout module 1108 may further comprise a discount coupon input 1126.The discount coupon input may comprise a discount coupon text field1128. Discount coupon text field 1128 may be used by a user to input adiscount code for the at least one of the product and/or order item inthe multi-restaurant order.

Checkout module 1108 may further comprise a tip input 1130. Tip input1130 may be used for the user to compensate at least one deliverprovider and/or delivery driver. Tip input 1130 may comprise a tip inputtext field. The tip input text field may be used by a user to input themonetary amount to compensate the at least one deliver provider and/ordelivery driver.

Checkout module 1108 may further comprise an order confirmation option1132. Upon the user selecting the order confirmation option, themulti-restaurant order may be transmitted to the plurality ofrestaurants associated with the multi-restaurant order, as illustratedin 1134. Upon the user selecting the order confirmation option, platform100 may provide the user with a user map. The user map may comprise avirtual mapping display. The map may further comprise a geolocationidentification of the delivery provider and/or the user overlayed on thevirtual mapping display.

FIG. 13 illustrates a process for a delivery provider, a deliverycoordinator, and/or delivery driver registration (collectively “deliveryprovider”). The registration may begin by the delivery providerlaunching platform 100, as illustrated in 1300. Upon launching platform100, the delivery provider may be directed to a delivery providerwelcome screen and/or page 1302. Delivery provider welcome screen and/orpage 1302 may comprise a prompt to choose whether the delivery providerhas an account or not, as illustrated in 1304.

Upon choosing that the delivery provider does have an account, theplatform may direct a user to a delivery provider login module(alternatively: screen, display, and/or page) 1306. Delivery providerlogin module 1306 may comprise a plurality of identification criteria.The plurality of identification criteria may comprise at least one ofthe plurality of delivery provider input requests. The plurality ofidentification criteria may be used to prompt the delivery provider toenter at least one input to securely log in. Upon logging in and/or alogin confirmation, the platform may prompt the delivery provider toprovide a current address and/or location. The current address and/orlocation may utilize a system to verify the validity of the address.Upon confirmation of the validity of the current address, the deliveryprovider may be directed to a home screen. The platform may furtherprompt the delivery provider to provide an acceptance to have theirgeolocation tracked when associated with a multi-restaurant order and/orwhen platform 100 is running.

Upon choosing that the delivery provider does not have an account, theplatform may direct the delivery provider to a delivery provider accountcreation interface and/or registration page 1308. In some embodiments,delivery provider account creation interface 1308 may comprise aplurality of delivery provider input requests and/or validation requests1310. Plurality of user input requests and/or validation requests 1310may comprise at least one of the following: a name, a biometricidentification, a username, a user image, an age, a location, a date ofbirth, an email address, a password, a 2-step verification, an identityverification, a human verification, and an identification card scan. Insome embodiments, the plurality of user input requests may beautomatically filled and/or verified via approval of at least onethird-party platform. The plurality of delivery provider input requestsmay be used for creating a delivery provider profile. In furtherembodiments, the account creation interface may comprise aquestionnaire. The questionnaire may be used to gather information aboutthe delivery provider such as, but not limited to, the following:

a) a vehicle type;

b) a food accommodation ability; and

c) financial information.

Upon the creation of the account, a confirmation display 1312 may beprovided. Confirmation display 1312 may be used as a result of the usersuccessfully completing the plurality of inputs and/or thequestionnaire. In some embodiments, confirmation display 1312 may causeplatform 100 to send a confirmation link to the delivery provider. Theconfirmation link may be provided via email, text message, and/or anyother notification previously mentioned. The confirmation link may beused to associate the email address to the user. The confirmation linkmay be further used to verify identification of the user.

Upon the confirmation and/or verification, the platform may directand/or launch, as illustrated in 1316, the delivery provider to adelivery provider home screen and/or page 1314.

Delivery provider home screen and/or page 1314, as illustrated in FIGS.14A and 14B, may comprise a delivery provider account module 1328. Thedelivery provider profile module may comprise a plurality of deliveryprovider information 1330. The plurality of delivery providerinformation may be used to store, access, display, and/or modify theinformation provided from the plurality of delivery provider inputrequests and/or information comprised in the delivery provider loginmodule.

The profile module may provide an editing option for personalinformation.

The profile module may further provide a means for payment list. Themeans for payment list may comprise a new payment receiving option. Thenew payment receiving option may prompt a delivery provider to fill outa virtual payment receiving form which, upon completion, adds the newmeans of payment to the means for payment list.

The delivery provider profile module my further provide a contactsupport menu 1318. Contact support menu 1318 may comprise a plurality ofcontact information. The plurality of contact information may comprise ameans to contact platform 100 associates, the plurality of restaurants,and/or users associated with the multi-restaurant order. The means tocontact may comprise a virtual fillable form and/or document.

The delivery provider home screen and/or page, as further illustrated inFIG. 13, may comprise a map 1320. Map 1320 may comprise a virtualmapping display. The map may further comprise a geolocationidentification of the delivery provider overlayed on the virtual mappingdisplay.

The platform, as illustrated in FIGS. 14A and 14B, may comprise a numberof steps and/or stages to coordinate and deliver the multi-restaurantorder once the multi-restaurant order has been requested and/orconfirmed. The process may start by providing a notification 1322 to aplurality of delivery providers. Notification 1322 may comprise any ofthe aforementioned notifications provided by platform 100. Notification1322 may comprise a link and/or hyperlink. Selecting the link and/orhyperlink may prompt platform 100 to launch and/or be activated on thedevice of each of the plurality of delivery providers, as illustrated in1300. Upon platform 100 launching via the at least one of the pluralityof delivery providers selecting the notification, at least one of theplurality of delivery providers (collectively “delivery provider”) maybe directed to delivery provider home screen and/or page 1314.

Delivery provider home screen and/or page 1314 may comprise an option1324 to be active on platform 100, or to be inactive on platform 100.Upon choosing to be active on platform 100, the delivery provider may beprovided the option to accept or decline the multi-restaurant order. Theoption to accept or decline may be limited to a timeframe. If no choiceis made within the given timeframe, platform may automatically declinethe multi-restaurant order for the delivery provider. Prior to theaccepting or declining, the delivery provider may be provided details ofthe multi-restaurant order.

Upon declining the multi-restaurant order, the delivery provider may bedirected to the delivery provider home scree and/or page.

Upon accepting, the delivery provider may be provided with a deliverymap 1332. The delivery map may comprise a plurality of pickupindications 1334. Plurality of pickup indications 1334 may comprise thegeolocations of the plurality of restaurants associated with themulti-restaurant order overlayed on the map. Plurality of pickupindications 1334 may comprise an estimated timeframe 1336 for the atleast one product and/or order item to be completed and/or to pick upthe at least one product and/or order item from each of the plurality ofrestaurants associated with the multi-restaurant order. The delivery mapmay further provide the delivery provider a shipping and/or deliverycost 1338. Shipping and/or delivery cost 1338 may comprise an amount offunds received by the delivery provider and/or platform 100 aftersuccessfully delivering each of the order items to the user.

It is noted that at any point during the delivery process of themulti-restaurant order, the delivery provider may have access to atleast one of the following:

-   -   a) a plurality of delivery details 1340 of the multi-restaurant        order;    -   b) contact information and/or an ability to communicate with at        least one user associated with the multi-restaurant order, as        illustrated in 1342;    -   c) contact information and/or an ability to communicate with at        least one associate of platform 100, as illustrated in 1318; and    -   d) contact information and/or an ability to communicate with at        least one other delivery provider associated with the        multi-restaurant order, as illustrated in 1346.

Upon accepting, the delivery provider may choose, indicate, associate,and/or confirm (collectively “confirm”) which of the at least oneproduct and/or order item to pick up, as illustrated in 1348. Upon theconfirming, platform 100 may then send a notification 1350 to the userof at least one of the following:

-   -   a) profile information of the delivery provider;    -   b) an estimated time for pickup of the at least one product        and/or order item;    -   c) an estimated time for delivery of the at least one product        and/or order item; and    -   d) a geolocation of the delivery provider.

Upon the delivery provider completing the picking up of the at least oneproduct and/or order item, platform 100 may transmit a notificationinforming pickup completion to the at least one of the followingassociated with the at least one multi-restaurant: the at least oneuser, the at least one restaurant, and/or other delivery providers. Uponthe delivery provider arriving at the restaurant and/or stop, thedelivery provider may update platform 100 with an availability 1356.Upon the delivery provider completing the picking up of the at least oneproduct and/or order item, platform 100 may further update the deliverymap as illustrated in step 1352 wherein the next destination is eitherto the location of the user and/or the location of the next restaurantassociated with the multi-restaurant order.

The delivery provider may, upon confirming, proceed to the secondrestaurant and/or stop in the multi-restaurant order, as illustrated instep 1354. Upon the delivery provider completing the picking up of theat least one product and/or order item, platform 100 may transmit anotification 1358 informing pickup completion to the at least one of thefollowing associated with the at least one multi-restaurant: the atleast one user, the at least one restaurant, and/or other deliveryproviders. Upon the delivery provider arriving at the second restaurantand/or stop, the delivery provider may update platform 100 with anavailability 1356. Upon the delivery provider completing the picking upof the at least one product and/or order item, platform 100 may furtherupdate the delivery map, as illustrated in 1360, wherein the nextdestination is either to the location of the user and/or the location ofthe next restaurant associated with the multi-restaurant order.

The delivery provider may, upon confirming, proceed to the thirdrestaurant and/or stop in the multi-restaurant order, as illustrated instep 1362. Upon the delivery provider completing the picking up of theat least one product and/or order item, platform 100 may transmit anotification 1366 informing pickup completion to the at least one of thefollowing associated with the at least one multi-restaurant: the atleast one user, the at least one restaurant, and/or other deliveryproviders. Upon the delivery provider arriving at the third restaurantand/or stop, the delivery provider may update platform 100 with anavailability 1364. Upon the delivery provider completing the picking upof the at least one product and/or order item, platform 100 may furtherupdate the delivery map, as illustrated in 1368, wherein the nextdestination is either to the location of the user and/or the location ofthe next restaurant associated with the multi-restaurant order.

The delivery provider may, for example, proceed to the furtherrestaurants and/or stops in the multi-restaurant order. Upon thedelivery provider completing the picking up of the at least one productand/or order item, platform 100 may transmit a notification informingpickup completion to the at least one of the following associated withthe at least one multi-restaurant: the at least one user, the at leastone restaurant, and/or other delivery providers. Upon the deliveryprovider completing the picking up of the at least one product and/ororder item, platform 100 may further update the delivery map wherein thenext destination is either to the location of the user and/or thelocation of the next restaurant associated with the multi-restaurantorder.

Upon the delivery provider picking up the requested products and/ororder items, the delivery provider may then deliver all or part of themulti-restaurant order to the user. Upon a successful delivery of themulti-restaurant order, the user and/or delivery provider may confirmthe delivery on platform 100, as illustrated in step 1370. Acongratulations message notification 1374 may be transmitted to the userand/or delivery provider upon the confirmation of delivery.

FIGS. 15A and 15B illustrates an embodiment in which the deliveryprovider accepts at least one product and/or order item of themulti-restaurant request, and the delivery provider is given a latencyto wait to pick up the at least one product and/or order item. Thislatency in pick up may be caused by the restaurant having a wait time,the product and/or order item being required to be at a predeterminedtemperature upon delivery to the user, the product and/or order itembeing a subsequent “course” for the multi-restaurant order, and/or theproduct and/or order item having to be combined and/or delivered at thesame time as the other products and/or order items in themulti-restaurant request.

FIG. 16 illustrates a flow chart of a restaurant launching system orplatform 100. Upon launching platform 100 at step 1600, the restaurantmay be forwarded to a restaurant welcome screen and/or page 1602.Restaurant welcome screen and/or page 1602 may comprise a prompt 1604 tochoose whether the user has an account or not.

Upon choosing that the user does have an account, the platform maydirect a user to a restaurant login module 1606 (alternatively: screen,display, and/or page). The restaurant login module may comprise aplurality of identification criteria. The plurality of identificationcriteria may comprise at least one of the plurality of restaurant inputrequests. The plurality of identification criteria may be used to promptthe restaurant to enter at least one input to securely log in. Uponlogging in and/or a login confirmation, the platform may prompt therestaurant to provide a current address in step 1608. The currentaddress may utilize a system to verify the validity of the address. Uponconfirmation of the validity of the current address, the restaurant maybe directed to a restaurant home screen 1612. Restaurant home screen1612 may provide a default address in step 712.

Upon choosing that the user does not have an account, the platform maydirect the user to an account creation interface and/or registrationpage 1614. In some embodiments, the account creation interface maycomprise a plurality of user input requests. The plurality of user inputrequests 1616 may comprise at least one of the following: a name, abiometric identification, a username, a user image, an age, a location,a date of birth, an email address, a password, a 2-step verification, anidentity verification, a human verification, and an identification cardscan. In some embodiments, the plurality of user input requests may beautomatically filled via approval of at least one third-party platform.The plurality of user input requests may be used for creating a userprofile. In further embodiments, the account creation interface maycomprise a questionnaire. The questionnaire may be used to assist inassociating a user with a plurality of recommended restaurants.

Upon the creation of the account, a confirmation display 1608 may beprovided. The confirmation display may be used as a result of the usersuccessfully completing the plurality of inputs and/or thequestionnaire. In some embodiments, the confirmation display may causeplatform 100 to send a confirmation link. The confirmation link may beprovided via email, text message, and/or any other notificationpreviously mentioned. The confirmation link may be used to associate theemail address to the user. The confirmation link may be further used toverify identification of the user.

Upon the confirmation and/or verification, the platform may direct therestaurant to restaurant home screen 1612.

Restaurant home screen and/or page 1612, as illustrated in FIG. 16B, maycomprise a restaurant profile module 1640. Restaurant profile module1640 may comprise a plurality of restaurant information 1642. Theplurality of restaurant information may be used to store, access,display, and/or modify the information provided from the plurality ofrestaurant input requests and/or information comprised in the restaurantlogin module.

The profile module may provide an editing option for personalinformation.

The profile module may further provide a means for payment list. Themeans for payment list may comprise a new payment receiving option. Thenew payment receiving option may prompt a restaurant to fill out avirtual payment receiving form which, upon completion, adds the newmeans of payment to the means for payment list.

The profile module may further provide a means for printing a bar code1660.

The restaurant profile module may further provide a contact support menu1638. Contact support menu 1638 may comprise a plurality of contactinformation. The plurality of contact information may comprise a meansto contact platform 100 associates, the plurality of restaurants, and/orusers associated with the multi-restaurant order. The means to contactmay comprise a virtual fillable form and/or document.

Restaurant home screen and/or page 1612, as further illustrated in FIG.16B, may comprise a map 1618. Map 1618 may comprise a virtual mappingdisplay. Map 1618 may further comprise a geolocation identification ofthe restaurant overlayed on the virtual mapping display.

The restaurant home screen and/or page may comprise an option 1620 to beactive on platform 100, or to be inactive on platform 100. Upon choosingto be active on platform 100, the restaurant may be provided the option1622 to accept (“confirm”) or decline the multi-restaurant order. Theoption to accept or decline may be limited to a timeframe. If no choiceis made within the given timeframe, platform may automatically declinethe multi-restaurant order for the restaurant. Prior to the accepting ordeclining, the restaurant may be provided details 1644 of themulti-restaurant order.

Upon confirming the order, the restaurant may be provided details of themulti-restaurant order. Upon confirming the order, the restaurant maysend the order to the at least one delivery provider associated with themulti-restaurant order, as illustrated in step 1624.

Upon confirming the order, the restaurant may be provided a tracking map1652. Tracking map 1654 may comprise the features of map 1618 inrelation to the confirmed multi-restaurant order. Tracking map 1654 mayfurther comprise delivery options 1656.

Upon confirming the order, the restaurant may determine and/or view ashipping cost 1658.

Upon confirming the order, the restaurant may comprise a rush hourconfiguration 1626. Rush hour configuration 1626 may comprise anestimation of time the restaurant will take to begin and/or prepare theat least one product and/or order item. The estimation may be based on aqueue and/or priority of products and/or order items prior to the atleast one product and/or order item of the multi-restaurant order. Therush hour configuration may occur during predetermined timeframes 1628(“Rush Hour”). The rush hour configuration may modify the estimatedpickup, preparation, and/or delivery time of the at least one productand/or order item and/or multi-restaurant order, as illustrated in step1650. The restaurant may further transmit a delay notification 1630 inthe event of any delay that occurs at in regard to the preparation ofthe at least one product and/or order item. Delay modification 1630 maybe presented to the restaurant in the form of selectable options suchas, for example, +5 min, +10 min, and +15 min, as illustrated in step1632. If the delay in the preparation of the at least one product and/ororder item is long enough, a route modification 1634 of the deliveryprovider may occur. The route modification may prompt a transmission ofa notification of the delay to the delivery provider and/or the user.

Upon a successful pickup of the products and/or order items, therestaurant and/or delivery provider may confirm the pickup, asillustrated in step 1656 on platform 100. A congratulations messagenotification 1636 may be transmitted to the restaurant and/or deliveryprovider upon the confirmation of pickup.

FIG. 17 illustrates a flow chart of additional options of the user afterthe confirmation of a multi-restaurant order. Track order option 1380may be made visible after the confirmation of a multi-restaurant order.Track order option 1380 may comprise map 1320. Map 1320 may comprise achat delivery option 1342 wherein the user may contact the at least onedelivery provider. Map 1320 may further comprise help option 750. Helpoption 750 may comprise a cancel order option 1382. Cancel order option1382 may be configured to not charge the user if cancelled within apredetermined amount of time of placing the order, as illustrated instep 1384.

FIG. 20 illustrates a context diagram of payment and funding flow usingplatform 100.

FIG. 21 illustrates a business flow diagram of platform 100.

Platform Operation

Hereinafter, detailed discussion of the operation of the platform 100 isprovided with reference to FIGS. 2-5, & 19 and associated methods ofcoordinating delivery of a dining experience to customers.

FIG. 2 is a flowchart of a method 200, according to an exemplaryembodiment of the present disclosure. The method 200 may includepresenting a menu or multiple menus from different restaurants tocustomers, at block 202. The menu may be an aggregated menu of allrestaurants 101 to which delivery to the customer is available. The menumay include processing and delivery times, prices, and other datarelated to a desired dining experience.

The customers may then assemble a request for the desired order items orrecipes based on the menu. In response thereto, the method 200 includesreceiving the request from the customer, including payment for the orderitems, at block 204. The request may include all necessary dataincluding delivery address, payment information, contact information,desired delivery time, desired extras or service options, and otherrelevant data. The request may be for immediately available delivery,delayed delivery, delivery at a particular date, delivery at aparticular address, requests for catering services, request forpersonnel to serve food (e.g., as a catering service), and/or any otheroptions presented through the provided menu.

Upon receipt of the request, the method 200 includes generatingprocessed requests 107 including recommended preparation times, desiredpickup times, delivery times, identification of a delivery provider 112,and other processed data, at block 206. The restaurants 101 may user thedesired pickup times and/or recommended preparation times to beginpreparing one or more portions of the individual requests.

The method 200 may also include coordinating completed order pickup withthe delivery provider 112, at block 208. The coordinating may includeproviding pickup addresses for the restaurants 101, pickup times,traffic data, weather data, and any other data related to facilitatingpickup of individual order item portions 114 to generate a completedorder 116. The coordinating may further include scheduling data andrequests to ensure the delivery provider 112 picks up order itemportions 114 at particular times to effectively deliver a desirabledining experience to the customer 104.

Upon successful pickup of order items 114, payment may be transmitted torestaurants 101, at block 210. Furthermore, upon successful delivery ofthe completed order 116 and dining experience to customer 104, paymentmay be transmitted to the delivery provider 112. It is noted thataccording to some embodiments, payment(s) may be transmitted at anytime, including in batches for multiple orders, depending upon anydesired implementation of the embodiments described herein.

FIG. 3 is a flowchart of a method 300, according to an embodiment of thepresent disclosure. The method 300 relates to creation of the menuprovided to customers at block 202.

The method 300 may include receiving a menu with associated orderitem/recipe preparation times from restaurants 101, at block 302. Thefood preparation times may be provided by restaurants 101, and mayinclude considerations such as seasonal variations or otherconsiderations.

The menu and preparation times may be processed at block 304, and storedat block 306. Storage may include storage in a database, storage system,storage apparatus, or other storage types by the delivery organizer 108.

Thereafter, or at substantially the same time, the delivery organizer108 may receive inventory availability from the restaurants 101, atblock 308. The inventory availability may be received on a scheduledbasis, may be received on-the-fly, may be received in real-time or insubstantially real-time, and may be used to determine availability ofparticular order items and recipes related to the stored menu itemsassociated with each restaurant 101.

The inventory availability may be updated at block 310, such thatcustomers are presented with up-to-date availability of order items suchthat incorrect multi-restaurant orders are reduced. The inventoryavailability may also include food preparation hours, operational hours,and other scheduling data.

Using the method 300, the delivery organizer 108 may ensure thatcustomers 104 are effectively provided up-to-date data related to orderitem availability and scheduling, to facilitate a pleasing diningexperience.

FIG. 4 is a flowchart of a method 400, according to an embodiment of thepresent disclosure. The method 400 relates to maintaining up-to-datedata as to availability of delivery providers 112.

The method 400 includes receiving schedule availability from deliveryproviders 112, at block 402. The schedule availability may includeoperational hours, particular delivery service member availability,geographical service data, vehicle types, vehicle equipment (heaters,coolers, refrigeration, etc.), vehicle storage capacity, estimatedtravel speed/times, and other data related to the delivery providers112.

The schedule availability and associated data may be stored by thedelivery organizer 108, at block 404. The storage may be substantiallysimilar to the storage user for restaurants data described above.Additionally, the schedule availability and associated data may beupdated on-the-fly, in real-time or substantially real-time, and/or onan ongoing basis. Accordingly, new service members or off-duty servicemembers of the delivery providers 112 may be quickly accounted for.

The method 400 further includes matching the stored scheduleavailability and associated data with the restaurants 101, at block 406.The matching may include determining geographical overlap, travel times,scheduling overlap, and other considerations. The matching may alsoinclude determining if particular delivery providers 112 have correctequipment for transporting completed orders 116 effectively, to ensure aconsistently pleasing dining experience for customers 104.

Rating systems and rankings may be provided for delivery providers 112,according to some embodiments. The rankings may also be used in thematching of block 406 to promote better delivery services forhigher-quality dining experiences. The matching data may be stored atblock 408 for relatively quick processing of desirable deliveryproviders 112 to restaurants 101 when receiving customer orders.

FIG. 5 is a flowchart of a method 500, according to an exemplaryembodiment of the present disclosure. The method 500 relates to blocks206 and 208 of method 200, and coordinating delivery of a diningexperience to a customer 104.

The method 500 includes processing a customer order request 106, atblock 502. The processing may include determining particular order itemsassociated with particular restaurants 101. The processing may alsoinclude determining desired delivery time, estimated preparation anddelivery times, estimated traffic delays, estimated weather delays, andother considerations.

Upon processing, the method 500 includes determining a matched deliveryprovider 112 based on the processing, at block 504. The matched ormatching delivery provider 112 may be determined based on storedhistorical matches (see FIG. 4), based on updated schedule availability,based on ranking, based on vehicle equipment, and other considerations.

After determining an appropriate match or matches, the method 500includes determining recommended preparation times based on the deliveryprovider and the stored menu data, at block 506. The recommendedpreparation times may take all available data, or a portion of availabledata, into consideration. For example, travel times, traffic delays,weather delays, storage and transport equipment, and otherconsiderations may be applicable to determining when a particular orderitem should begin to be prepared at a restaurant 101.

Upon establishing and transmitting food preparation data includingpreparation times, delivery windows, estimated pickup times, and otherdata, to restaurants 101, the method 500 may include coordinatingcompleted order item pickup with the delivery provider 112 andrestaurants 101, at block 508. The coordination may include transmittingassociated data to both the delivery provider 112 and restaurants 101such that the restaurants and delivery providers have the same data andcan effectively deliver a consistent and pleasing dining experience tothe customers 104.

FIG. 19 is a flow chart of method 2500 incorporating elements of methods200-500.

Computing Device Architecture

At least a portion of the platform and/or system 100 and associatedcomponents may include aspects embodied as, for example, but not belimited to, a website, a web application, a desktop application, backendapplication, and a mobile application compatible with a computing device600. Furthermore, various embodiments may provide for a computing deviceassociated with various aspects of the delivery provider hardware (e.g.,vehicle storage and sensing mechanisms associated with the deliveredorder items, to monitor and report aspects of the food items in deliveryroute) and various aspects of the kitchen preparing the order items(e.g., as relating to the preparation and storage of the order items,and to monitor and report aspects of the food items during preparationand storage). Said computing device may be configured for bi-directionalcommunication with various aspects of the platform. The computing device600 may comprise, but not be limited to the following:

Mobile computing devices, such as, but not limited to, a laptop, atablet, a smartphone, a drone, a wearable, an embedded device, ahandheld device, an Arduino, an industrial device, or a remotelyoperable recording device;

A supercomputer, an exa-scale supercomputer, a mainframe, or a quantumcomputer;

A minicomputer, wherein the minicomputer computing device comprises, butis not limited to, an IBM AS400/iSeries/System I, A DEC VAX/PDP, aHP3000, a Honeywell-Bull DPS, a Texas Instruments TI-990, or a WangLaboratories VS Series;

A microcomputer, wherein the microcomputer computing device comprises,but is not limited to, a server, wherein a server may be rack mounted, aworkstation, an industrial device, a raspberry pi, a desktop, or anembedded device;

System 100 may be hosted on a centralized server or a cloud computingservice. Although method 200, and methods 300, 400, and 500, have beendescribed to be performed by a computing device 600, it should beunderstood that, in some embodiments, different operations may beperformed by a plurality of the computing devices 600 in operativecommunication at least one network.

Embodiments of the present disclosure may comprise a system having acentral processing unit (CPU) 620, a bus 630, a memory unit 640, a powersupply unit (PSU) 650, and one or more Input/Output (I/O) units. The CPU620 coupled to the memory unit 640 and the plurality of I/O units 660via the bus 630, all of which are powered by the PSU 650. It should beunderstood that, in some embodiments, each disclosed unit may actuallybe a plurality of such units for the purposes of redundancy, highavailability, and/or performance. The combination of the presentlydisclosed units is configured to perform the stages any method disclosedherein.

FIG. 6 is a block diagram of a system including computing device 600.Consistent with an embodiment of the disclosure, the aforementioned CPU620, the bus 630, the memory unit 640, a PSU 650, and the plurality ofI/O units 660 may be implemented in a computing device, such ascomputing device 600 of FIG. 6. Any suitable combination of hardware,software, or firmware may be used to implement the aforementioned units.For example, the CPU 620, the bus 630, and the memory unit 640 may beimplemented with computing device 600 or any of other computing devices600, in combination with computing device 600. The aforementionedsystem, device, and components are examples and other systems, devices,and components may comprise the aforementioned CPU 620, the bus 630, thememory unit 640, consistent with embodiments of the disclosure.

At least one computing device 600 may be embodied as any of thecomputing elements illustrated in all of the attached figures. Acomputing device 600 does not need to be electronic, nor even have a CPU620, nor bus 630, nor memory unit 640. The definition of the computingdevice 600 to a person having ordinary skill in the art is “A devicethat computes, especially a programmable electronic machine thatperforms high-speed mathematical or logical operations or thatassembles, stores, correlates, or otherwise processes information.” Anydevice which processes information qualifies as a computing device 600,especially if the processing is purposeful.

With reference to FIG. 6, a system consistent with an embodiment of thedisclosure may include a computing device, such as computing device 600.In a basic configuration, computing device 600 may include at least oneclock module 610, at least one CPU 620, at least one bus 630, and atleast one memory unit 640, at least one PSU 650, and at least one I/O660 module, wherein I/O module may be comprised of, but not limited to anon-volatile storage sub-module 661, a communication sub-module 662, asensors sub-module 663, and a peripherals sub-module 664.

A system consistent with an embodiment of the disclosure the computingdevice 600 may include the clock module 610 may be known to a personhaving ordinary skill in the art as a clock generator, which producesclock signals. Clock signal is a particular type of signal thatoscillates between a high and a low state and is used like a metronometo coordinate actions of digital circuits. Most integrated circuits(ICs) of sufficient complexity use a clock signal in order tosynchronize different parts of the circuit, cycling at a rate slowerthan the worst-case internal propagation delays. The preeminent exampleof the aforementioned integrated circuit is the CPU 620, the centralcomponent of modern computers, which relies on a clock. The onlyexceptions are asynchronous circuits such as asynchronous CPUs. Theclock 610 can comprise a plurality of embodiments, such as, but notlimited to, single-phase clock which transmits all clock signals oneffectively 1 wire, two-phase clock which distributes clock signals ontwo wires, each with non-overlapping pulses, and four-phase clock whichdistributes clock signals on 4 wires.

Many computing devices 600 use a “clock multiplier” which multiplies alower frequency external clock to the appropriate clock rate of the CPU620. This allows the CPU 620 to operate at a much higher frequency thanthe rest of the computer, which affords performance gains in situationswhere the CPU 620 does not need to wait on an external factor (likememory 640 or input/output 660). Some embodiments of the clock 610 mayinclude dynamic frequency change, where, the time between clock edgescan vary widely from one edge to the next and back again.

A system consistent with an embodiment of the disclosure the computingdevice 600 may include the CPU unit 620 comprising at least one CPU Core621. A plurality of CPU cores 621 may comprise identical the CPU cores621, such as, but not limited to, homogeneous multi-core systems. It isalso possible for the plurality of CPU cores 621 to comprise differentthe CPU cores 621, such as, but not limited to, heterogeneous multi-coresystems, big.LITTLE systems and some AMD accelerated processing units(APU). The CPU unit 620 reads and executes program instructions whichmay be used across many application domains, for example, but notlimited to, general purpose computing, embedded computing, networkcomputing, digital signal processing (DSP), and graphics processing(GPU). The CPU unit 620 may run multiple instructions on separate CPUcores 621 at the same time. The CPU unit 620 may be integrated into atleast one of a single integrated circuit die and multiple dies in asingle chip package. The single integrated circuit die and multiple diesin a single chip package may contain a plurality of other aspects of thecomputing device 600, for example, but not limited to, the clock 610,the CPU 620, the bus 630, the memory 640, and I/O 660.

The CPU unit 620 may contain cache 622 such as, but not limited to, alevel 1 cache, level 2 cache, level 3 cache or combination thereof. Theaforementioned cache 622 may or may not be shared amongst a plurality ofCPU cores 621. The cache 622 sharing comprises at least one of messagepassing and inter-core communication methods may be used for the atleast one CPU Core 621 to communicate with the cache 622. The inter-corecommunication methods may comprise, but not limited to, bus, ring,two-dimensional mesh, and crossbar. The aforementioned CPU unit 620 mayemploy symmetric multiprocessing (SMP) design.

The plurality of the aforementioned CPU cores 621 may comprise softmicroprocessor cores on a single field programmable gate array (FPGA),such as semiconductor intellectual property cores (IP Core). Theplurality of CPU cores 621 architecture may be based on at least one of,but not limited to, Complex instruction set computing (CISC), Zeroinstruction set computing (ZISC), and Reduced instruction set computing(RISC). At least one of the performance-enhancing methods may beemployed by the plurality of the CPU cores 621, for example, but notlimited to Instruction-level parallelism (ILP) such as, but not limitedto, superscalar pipelining, and Thread-level parallelism (TLP).

Consistent with the embodiments of the present disclosure, theaforementioned computing device 600 may employ a communication systemthat transfers data between components inside the aforementionedcomputing device 600, and/or the plurality of computing devices 600. Theaforementioned communication system will be known to a person havingordinary skill in the art as a bus 630. The bus 630 may embody internaland/or external plurality of hardware and software components, forexample, but not limited to a wire, optical fiber, communicationprotocols, and any physical arrangement that provides the same logicalfunction as a parallel electrical bus. The bus 630 may comprise at leastone of, but not limited to a parallel bus, wherein the parallel buscarry data words in parallel on multiple wires, and a serial bus,wherein the serial bus carry data in bit-serial form. The bus 630 mayembody a plurality of topologies, for example, but not limited to, amultidrop/electrical parallel topology, a daisy chain topology, and aconnected by switched hubs, such as USB bus. The bus 630 may comprise aplurality of embodiments, for example, but not limited to: Internal databus (data bus) 631/Memory bus; Control bus 632; Address bus 633; SystemManagement Bus (SMBus); Front-Side-Bus (FSB); External Bus Interface(EBI); Local bus; Expansion bus; Lightning bus; Controller Area Network(CAN bus); Camera Link; and/or ExpressCard.

The bus 630 may also comprise a plurality of embodiments, for example,but not limited to: Advanced Technology management Attachment (ATA),including embodiments and derivatives such as, but not limited to,Integrated Drive Electronics (IDE)/Enhanced IDE (EIDE), ATA PacketInterface (ATAPI), Ultra-Direct Memory Access (UDMA), Ultra ATA(UATA)/Parallel ATA (PATA)/Serial ATA (SATA), CompactFlash (CF)interface, Consumer Electronics ATA (CE-ATA)/Fiber Attached TechnologyAdapted (FATA), Advanced Host Controller Interface (AHCI), SATA Express(SATAe)/External SATA (eSATA), including the powered embodimenteSATAp/Mini-SATA (mSATA), and Next Generation Form Factor (NGFF)/M.2.

The bus 630 may also comprise a plurality of embodiments, for example,but not limited to: Small Computer System Interface (SCSI)/SerialAttached SCSI (SAS); HyperTransport; InfiniBand; RapidIO; MobileIndustry Processor Interface (MIPI); Coherent Processor Interface(CAPI); Plug-n-play; 1-Wire.

The bus 630 may also comprise a plurality of embodiments, for example,but not limited to: Peripheral Component Interconnect (PCI), includingembodiments such as, but not limited to, Accelerated Graphics Port(AGP), Peripheral Component Interconnect eXtended (PCI-X), PeripheralComponent Interconnect Express (PCI-e) (i.e., PCI Express Mini Card, PCIExpress M.2 [Mini PCIe v2], PCI Express External Cabling [ePCIe], andPCI Express OCuLink [Optical Copper{Cu} Link]), Express Card,AdvancedTCA, AMC, Universal 10, Thunderbolt/Mini DisplayPort, MobilePCIe (M-PCIe), U.2, and Non-Volatile Memory Express (NVMe)/Non-VolatileMemory Host Controller Interface Specification (NVMHCIS).

The bus 630 may further comprise a plurality of embodiments, forexample, but not limited to: Industry Standard Architecture (ISA),including embodiments such as, but not limited to Extended ISA (EISA),PC/XT-bus/PC/AT-bus/PC/104 bus (e.g., PC/104-Plus, PCI/104-Express,PCI/104, and PCI-104), and Low Pin Count (LPC).

The bus 630 may comprise a Music Instrument Digital Interface (MIDI), ora Universal Serial Bus (USB), including embodiments such as, but notlimited to, Media Transfer Protocol (MTP)/Mobile High-Definition Link(MHL), Device Firmware Upgrade (DFU), wireless USB, InterChip USB, IEEE1394 Interface/Firewire, Thunderbolt, and eXtensible Host ControllerInterface (xHCI).

Consistent with the embodiments of the present disclosure, theaforementioned computing device 600 may employ hardware integratedcircuits that store information for immediate use in the computingdevice 600, know to the person having ordinary skill in the art asprimary storage or memory 640. The memory 640 operates at high speed,distinguishing it from the non-volatile storage sub-module 661, whichmay be referred to as secondary or tertiary storage, which providesslow-to-access information but offers higher capacities at lower cost.The contents contained in memory 640, may be transferred to secondarystorage via techniques such as, but not limited to, virtual memory andswap. The memory 640 may be associated with addressable semiconductormemory, such as integrated circuits consisting of silicon-basedtransistors, used for example as primary storage but also other purposesin the computing device 600. The memory 640 may comprise a plurality ofembodiments, such as, but not limited to volatile memory, non-volatilememory, and semi-volatile memory. It should be understood by a personhaving ordinary skill in the art that the ensuing are non-limitingexamples of the aforementioned memory:

Volatile memory which requires power to maintain stored information, forexample, but not limited to, Dynamic Random-Access Memory (DRAM) 641,Static Random-Access Memory (SRAM) 642, CPU Cache memory 625, AdvancedRandom-Access Memory (A-RAM), and other types of primary storage such asRandom-Access Memory (RAM).

Non-volatile memory which can retain stored information even after poweris removed, for example, but not limited to, Read-Only Memory (ROM) 643,Programmable ROM (PROM) 644, Erasable PROM (EPROM) 645, ElectricallyErasable PROM (EEPROM) 646 (e.g., flash memory and ElectricallyAlterable PROM [EAPROM]), Mask ROM (MROM), One Time Programable (OTP)ROM/Write Once Read Many (WORM), Ferroelectric RAM (FeRAM), ParallelRandom-Access Machine (PRAM), Split-Transfer Torque RAM (STT-RAM),Silicon Oxime Nitride Oxide Silicon (SONOS), Resistive RAM (RRAM), NanoRAM (NRAM), 3D XPoint, Domain-Wall Memory (DWM), and millipede memory.

Semi-volatile memory which may have some limited non-volatile durationafter power is removed but loses data after said duration has passed.Semi-volatile memory provides high performance, durability, and othervaluable characteristics typically associated with volatile memory,while providing some benefits of true non-volatile memory. Thesemi-volatile memory may comprise volatile and non-volatile memoryand/or volatile memory with battery to provide power after power isremoved. The semi-volatile memory may comprise, but not limited tospin-transfer torque RAM (STT-RAM).

Consistent with the embodiments of the present disclosure, theaforementioned computing device 600 may employ the communication systembetween an information processing system, such as the computing device600, and the outside world, for example, but not limited to, human,environment, and another computing device 600. The aforementionedcommunication system will be known to a person having ordinary skill inthe art as I/O 660. The I/O module 660 regulates a plurality of inputsand outputs with regard to the computing device 600, wherein the inputsare a plurality of signals and data received by the computing device600, and the outputs are the plurality of signals and data sent from thecomputing device 600. The I/O module 660 interfaces a plurality ofhardware, such as, but not limited to, non-volatile storage 661,communication devices 662, sensors 663, and peripherals 664. Theplurality of hardware is used by the at least one of, but not limitedto, human, environment, and another computing device 600 to communicatewith the present computing device 600. The I/O module 660 may comprise aplurality of forms, for example, but not limited to channel I/O, portmapped I/O, asynchronous I/O, and Direct Memory Access (DMA).

Consistent with the embodiments of the present disclosure, theaforementioned computing device 600 may employ the non-volatile storagesub-module 661, which may be referred to by a person having ordinaryskill in the art as one of secondary storage, external memory, tertiarystorage, off-line storage, and auxiliary storage. The non-volatilestorage sub-module 661 may not be accessed directly by the CPU 620without using intermediate area in the memory 640. The non-volatilestorage sub-module 661 does not lose data when power is removed and maybe two orders of magnitude less costly than storage used in memorymodule, at the expense of speed and latency. The non-volatile storagesub-module 661 may comprise a plurality of forms, such as, but notlimited to, Direct Attached Storage (DAS), Network Attached Storage(NAS), Storage Area Network (SAN), nearline storage, Massive Array ofIdle Disks (MAID), Redundant Array of Independent Disks (RAID), devicemirroring, off-line storage, and robotic storage. The non-volatilestorage sub-module (661) may comprise a plurality of embodiments, suchas, but not limited to:

Optical storage, for example, but not limited to, Compact Disk (CD)(CD-ROM/CD-R/CD-RW), Digital Versatile Disk (DVD)(DVD-ROM/DVD-R/DVD+R/DVD-RW/DVD+RW/DVD±RW/DVD+R DL/DVD-RAM/HD-DVD),Blu-ray Disk (BD) (BD-ROM/BD-R/BD-RE/BD-R DL/BD-RE DL), andUltra-Density Optical (UDO); and

Semiconductor storage, for example, but not limited to, flash memory,such as, but not limited to, USB flash drive, Memory card, SubscriberIdentity Module (SIM) card, Secure Digital (SD) card, Smart Card,CompactFlash (CF) card, Solid-State Drive (SSD) and memristor.

The non-volatile storage sub-module (661) may also comprise a pluralityof embodiments, such as, but not limited to: Magnetic storage such as,but not limited to, Hard Disk Drive (HDD), tape drive, carousel memory,and Card Random-Access Memory (CRAM); Phase-change memory; Holographicdata storage such as Holographic Versatile Disk (HVD); Molecular Memory;and/or Deoxyribonucleic Acid (DNA) digital data storage.

Consistent with the embodiments of the present disclosure, theaforementioned computing device 600 may employ the communicationsub-module 662 as a subset of the I/O 660, which may be referred to by aperson having ordinary skill in the art as at least one of, but notlimited to, computer network, data network, and network. The networkallows computing devices 600 to exchange data using connections, whichmay be known to a person having ordinary skill in the art as data links,between network nodes. The nodes comprise network computer devices 600that originate, route, and terminate data. The nodes are identified bynetwork addresses and can include a plurality of hosts consistent withthe embodiments of a computing device 600. The aforementionedembodiments include, but not limited to personal computers, phones,servers, drones, and networking devices such as, but not limited to,hubs, switches, routers, modems, and firewalls.

Two nodes can be said are networked together, when one computing device600 is able to exchange information with the other computing device 600,whether or not they have a direct connection with each other. Thecommunication sub-module 662 supports a plurality of applications andservices, such as, but not limited to World Wide Web (WWW), digitalvideo and audio, shared use of application and storage computing devices600, printers/scanners/fax machines, email/online chat/instantmessaging, remote control, distributed computing, etc. The network maycomprise a plurality of transmission mediums, such as, but not limitedto conductive wire, fiber optics, and wireless. The network may comprisea plurality of communications protocols to organize network traffic,wherein application-specific communications protocols are layered, maybe known to a person having ordinary skill in the art as carried aspayload, over other more general communications protocols. The pluralityof communications protocols may comprise, but not limited to, IEEE 802,ethernet, Wireless LAN (WLAN/Wi-Fi), Internet Protocol (IP) suite (e.g.,TCP/IP, UDP, Internet Protocol version 4 [IPv4], and Internet Protocolversion 6 [IPv6]), Synchronous Optical Networking (SONET)/SynchronousDigital Hierarchy (SDH), Asynchronous Transfer Mode (ATM), and cellularstandards (e.g., Global System for Mobile Communications [GSM], GeneralPacket Radio Service [GPRS], Code-Division Multiple Access [CDMA], andIntegrated Digital Enhanced Network [IDEN]).

The communication sub-module 662 may comprise a plurality of size,topology, traffic control mechanism and organizational intent. Thecommunication sub-module 662 may comprise a plurality of embodiments,such as, but not limited to: Wired communications, such as, but notlimited to, coaxial cable, phone lines, twisted pair cables (ethernet),and InfiniBand; Wireless communications, such as, but not limited to,communications satellites, cellular systems, radio frequency/spreadspectrum technologies, IEEE 802.11 Wi-Fi, Bluetooth, NFC, free-spaceoptical communications, terrestrial microwave, and Infrared (IR)communications. Wherein cellular systems embody technologies such as,but not limited to, 3G, 4G (such as WiMax and LTE), and 5G (short andlong wavelength); Parallel communications, such as, but not limited to,LPT ports; Serial communications, such as, but not limited to, RS-232and USB; Fiber Optic communications, such as, but not limited to,Single-mode optical fiber (SMF) and Multi-mode optical fiber (MMF);and/or Power Line communications.

The aforementioned network may comprise a plurality of layouts, such as,but not limited to, bus network such as ethernet, star network such asWi-Fi, ring network, mesh network, fully connected network, and treenetwork. The network can be characterized by its physical capacity orits organizational purpose. Use of the network, including userauthorization and access rights, differ accordingly. Thecharacterization may include, but not limited to nanoscale network,Personal Area Network (PAN), Local Area Network (LAN), Home Area Network(HAN), Storage Area Network (SAN), Campus Area Network (CAN), backbonenetwork, Metropolitan Area Network (MAN), Wide Area Network (WAN),enterprise private network, Virtual Private Network (VPN), and GlobalArea Network (GAN).

Consistent with the embodiments of the present disclosure, theaforementioned computing device 600 may employ the sensors sub-module663 as a subset of the I/O 660. The sensors sub-module 663 comprises atleast one of the devices, modules, and subsystems whose purpose is todetect events or changes in its environment and send the information tothe computing device 600. Sensors are sensitive to the measuredproperty, are not sensitive to any property not measured, but may beencountered in its application, and do not significantly influence themeasured property. The sensors sub-module 663 may comprise a pluralityof digital devices and analog devices, wherein if an analog device isused, an Analog to Digital (A-to-D) converter must be employed tointerface the said device with the computing device 600. The sensors maybe subject to a plurality of deviations that limit sensor accuracy. Thesensors sub-module 663 may comprise a plurality of embodiments, such as,but not limited to, chemical sensors, automotive sensors,acoustic/sound/vibration sensors, electric current/electricpotential/magnetic/radio sensors,environmental/weather/moisture/humidity sensors, flow/fluid velocitysensors, ionizing radiation/particle sensors, navigation sensors,position/angle/displacement/distance/speed/acceleration sensors,imaging/optical/light sensors, pressure sensors, force/density/levelsensors, thermal/temperature sensors, and proximity/presence sensors. Itshould be understood by a person having ordinary skill in the art thatthe ensuing are non-limiting examples of the aforementioned sensors:

Chemical sensors, such as, but not limited to, breathalyzer, carbondioxide sensor, carbon monoxide/smoke detector, catalytic bead sensor,chemical field-effect transistor, chemiresistor, electrochemical gassensor, electronic nose, electrolyte-insulator-semiconductor sensor,energy-dispersive X-ray spectroscopy, fluorescent chloride sensors,holographic sensor, hydrocarbon dew point analyzer, hydrogen sensor,hydrogen sulfide sensor, infrared point sensor, ion-selective electrode,nondispersive infrared sensor, microwave chemistry sensor, nitrogenoxide sensor, olfactometer, optode, oxygen sensor, ozone monitor,pellistor, pH glass electrode, potentiometric sensor, redox electrode,zinc oxide nanorod sensor, and biosensors (such as nanosensors).

Automotive sensors, such as, but not limited to, air flow meter/massairflow sensor, air-fuel ratio meter, AFR sensor, blind spot monitor,engine coolant/exhaust gas/cylinder head/transmission fluid temperaturesensor, hall effect sensor, wheel/automatic transmission/turbine/vehiclespeed sensor, airbag sensors, brake fluid/engine crankcase/fuel/oil/tirepressure sensor, camshaft/crankshaft/throttle position sensor, fuel/oillevel sensor, knock sensor, light sensor, MAP sensor, oxygen sensor(o2), parking sensor, radar sensor, torque sensor, variable reluctancesensor, and water-in-fuel sensor.

Acoustic, sound and vibration sensors, such as, but not limited to,microphone, lace sensor (guitar pickup), seismometer, sound locator,geophone, and hydrophone.

Electric current, electric potential, magnetic, and radio sensors, suchas, but not limited to, current sensor, Daly detector, electroscope,electron multiplier, faraday cup, galvanometer, hall effect sensor, hallprobe, magnetic anomaly detector, magnetometer, magnetoresistance, MEMSmagnetic field sensor, metal detector, planar hall sensor, radiodirection finder, and voltage detector.

Environmental, weather, moisture, and humidity sensors, such as, but notlimited to, actinometer, air pollution sensor, bedwetting alarm,ceilometer, dew warning, electrochemical gas sensor, fish counter,frequency domain sensor, gas detector, hook gauge evaporimeter,humistor, hygrometer, leaf sensor, lysimeter, pyranometer, pyrgeometer,psychrometer, rain gauge, rain sensor, seismometers, SNOTEL, snow gauge,soil moisture sensor, stream gauge, and tide gauge.

Flow and fluid velocity sensors, such as, but not limited to, air flowmeter, anemometer, flow sensor, gas meter, mass flow sensor, and watermeter.

Ionizing radiation and particle sensors, such as, but not limited to,cloud chamber, Geiger counter, Geiger-Muller tube, ionization chamber,neutron detection, proportional counter, scintillation counter,semiconductor detector, and thermoluminescent dosimeter.

Navigation sensors, such as, but not limited to, air speed indicator,altimeter, attitude indicator, depth gauge, fluxgate compass, gyroscope,inertial navigation system, inertial reference unit, magnetic compass,MHD sensor, ring laser gyroscope, turn coordinator, variometer,vibrating structure gyroscope, and yaw rate sensor.

Position, angle, displacement, distance, speed, and accelerationsensors, such as, but not limited to, accelerometer, displacementsensor, flex sensor, free fall sensor, gravimeter, impact sensor, laserrangefinder, LIDAR, odometer, photoelectric sensor, position sensor suchas, but not limited to, GPS or Glonass, angular rate sensor, shockdetector, ultrasonic sensor, tilt sensor, tachometer, ultra-widebandradar, variable reluctance sensor, and velocity receiver.

Imaging, optical and light sensors, such as, but not limited to, CMOSsensor, colorimeter, contact image sensor, electro-optical sensor,infra-red sensor, kinetic inductance detector, LED as light sensor,light-addressable potentiometric sensor, Nichols radiometer, fiber-opticsensors, optical position sensor, thermopile laser sensor,photodetector, photodiode, photomultiplier tubes, phototransistor,photoelectric sensor, photoionization detector, photomultiplier,photoresistor, photoswitch, phototube, scintillometer, Shack-Hartmann,single-photon avalanche diode, superconducting nanowire single-photondetector, transition edge sensor, visible light photon counter, andwavefront sensor.

Pressure sensors, such as, but not limited to, barograph, barometer,boost gauge, bourdon gauge, hot filament ionization gauge, ionizationgauge, McLeod gauge, Oscillating U-tube, permanent downhole gauge,piezometer, Pirani gauge, pressure sensor, pressure gauge, tactilesensor, and time pressure gauge.

Force, Density, and Level sensors, such as, but not limited to,bhangmeter, hydrometer, force gauge or force sensor, level sensor, loadcell, magnetic level or nuclear density sensor or strain gauge,piezocapacitive pressure sensor, piezoelectric sensor, torque sensor,and viscometer.

Thermal and temperature sensors, such as, but not limited to, bolometer,bimetallic strip, calorimeter, exhaust gas temperature gauge, flamedetection/pyrometer, Gardon gauge, Golay cell, heat flux sensor,microbolometer, microwave radiometer, net radiometer,infrared/quartz/resistance thermometer, silicon bandgap temperaturesensor, thermistor, and thermocouple.

Proximity and presence sensors, such as, but not limited to, alarmsensor, doppler radar, motion detector, occupancy sensor, proximitysensor, passive infrared sensor, reed switch, stud finder, triangulationsensor, touch switch, and wired glove.

Consistent with the embodiments of the present disclosure, theaforementioned computing device 600 may employ the peripheralssub-module 662 as a subset of the I/O 660. The peripheral sub-module 664comprises ancillary devices uses to put information into and getinformation out of the computing device 600. There are 3 categories ofdevices comprising the peripheral sub-module 664, which exist based ontheir relationship with the computing device 600, input devices, outputdevices, and input/output devices. Input devices send at least one ofdata and instructions to the computing device 600. Input devices can becategorized based on, but not limited to: Modality of input, such as,but not limited to, mechanical motion, audio, visual, and tactile;Whether the input is discrete, such as but not limited to, pressing akey, or continuous such as, but not limited to position of a mouse; Thenumber of degrees of freedom involved, such as, but not limited to,two-dimensional mice vs three-dimensional mice used for Computer-AidedDesign (CAD) applications; Output devices provide output from thecomputing device 600. Output devices convert electronically generatedinformation into a form that can be presented to humans. Input/outputdevices perform that perform both input and output functions.

It should be understood by a person having ordinary skill in the artthat the ensuing are non-limiting embodiments of the aforementionedperipheral sub-module 664: Input Devices; Human Interface Devices (HID),such as, but not limited to, pointing device (e.g., mouse, touchpad,joystick, touchscreen, game controller/gamepad, remote, light pen, lightgun, Wii remote, jog dial, shuttle, and knob), keyboard, graphicstablet, digital pen, gesture recognition devices, magnetic ink characterrecognition, Sip-and-Puff (SNP) device, and Language Acquisition Device(LAD).

High degree of freedom devices, that require up to six degrees offreedom such as, but not limited to, camera gimbals, Cave AutomaticVirtual Environment (CAVE), and virtual reality systems.

Video Input devices are used to digitize images or video from theoutside world into the computing device 600. The information can bestored in a multitude of formats depending on the user's requirement.Examples of types of video input devices include, but not limited to,digital camera, digital camcorder, portable media player, web cam,Microsoft Kinect, image scanner, fingerprint scanner, barcode reader, 3Dscanner, laser rangefinder, eye gaze tracker, computed tomography,magnetic resonance imaging, positron emission tomography, medicalultrasonography, TV tuner, and iris scanner.

Audio input devices are used to capture sound. In some cases, an audiooutput device can be used as an input device, in order to captureproduced sound. Audio input devices allow a user to send audio signalsto the computing device 600 for at least one of processing, recording,and carrying out commands. Devices such as microphones allow users tospeak to the computer in order to record a voice message or navigatesoftware. Aside from recording, audio input devices are also used withspeech recognition software. Examples of types of audio input devicesinclude, but not limited to microphone, Musical Instrumental DigitalInterface (MIDI) devices such as, but not limited to a keyboard, andheadset.

Data AcQuisition (DAQ) devices covert at least one of analog signals andphysical parameters to digital values for processing by the computingdevice 600. Examples of DAQ devices may include, but not limited to,Analog to Digital Converter (ADC), data logger, signal conditioningcircuitry, multiplexer, and Time to Digital Converter (TDC).

Output Devices may further comprise, but not be limited to:

Display devices, which convert electrical information into visual form,such as, but not limited to, monitor, TV, projector, and Computer OutputMicrofilm (COM). Display devices can use a plurality of underlyingtechnologies, such as, but not limited to, Cathode-Ray Tube (CRT),Thin-Film Transistor (TFT), Liquid Crystal Display (LCD), OrganicLight-Emitting Diode (OLED), MicroLED, E Ink Display (ePaper) andRefreshable Braille Display (Braille Terminal).

Printers, such as, but not limited to, inkjet printers, laser printers,3D printers, solid ink printers and plotters.

Audio and Video (AV) devices, such as, but not limited to, speakers,headphones, amplifiers and lights, which include lamps, strobes, DJlighting, stage lighting, architectural lighting, special effectlighting, and lasers.

Other devices such as Digital to Analog Converter (DAC)

Input/Output Devices may further comprise, but not be limited to,touchscreens, networking device (e.g., devices disclosed in network 662sub-module), data storage device (non-volatile storage 661), facsimile(FAX), and graphics/sound cards.

All rights including copyrights in the code included herein are vestedin and the property of the Applicant. The Applicant retains and reservesall rights in the code included herein, and grants permission toreproduce the material only in connection with reproduction of thegranted patent and for no other purpose.

Aspects

The following disclose various Aspects of the present disclosure. Thevarious Aspects are not to be construed as patent claims unless thelanguage of the Aspect appears as a patent claim. The Aspects describevarious non-limiting embodiments of the present disclosure.

Aspects include:

Aspect 1: Roles:

1) End User: Requesting multi-order orders, searching the application byrestaurant, type of food, diet, etc. And configure the payment method toperform the checkout process.

2) Delivery Partner: Will be responsible for collecting the orders anddelivering them to the end user in the expected time.

3) Restaurant: Will prepare the orders (meals) according to the scheduleplanned by the platform.

4) Administrator: Will make general settings within the platform. Hewill also be able to participate in the process of approval/rejectionfor the registration of Restaurants and Delivery partners in case it isnecessary.

Aspect 2: End User Cycle—The life cycle of the end user within theplatform includes the following events:

1) End User registration/Authorization.

2) Search for meals, restaurants, types of ingredients, types of diets,scores, discounts.

3) Creation of an order with multiple orders.

4) Order confirmation and payment data (it will allow to divide thepayment between the guests who have the application installed in theircell phones).

5) Order tracking.

6) Reception of the order and qualification of the service.

Aspect 3: Restaurant Life Cycle—The life cycle of the Restaurant withinthe platform includes the following events:

1) Restaurant Registration

2) Process validation

-   -   a. Terms and Conditions    -   b. Presentation of required legal documents    -   c. Bank account to receive payment    -   d. Approval/Rejection by the platform

3) Profile configuration for restaurants

-   -   a. Creation of the food catalog    -   b. Uploading images    -   c. Detail of ingredients    -   d. Diet details    -   e. Preparation times for each meal    -   f. Delay times at peak times

4) Order Confirmation/Rejection

5) Orders Preparation

6) Food ready to be delivered to the delivery partner

Aspect 4: Delivery Partner Life Cycle—The life cycle of the DeliveryPartner within the platform includes the following events:

1) Delivery Partner Registration

2) Process validation

-   -   a. Presentation of required legal documents    -   b. Bank account to receive payment    -   c. Terms and conditions    -   d. Approval/Rejection by the platform

3) Order Acceptance/Rejection

4) Order pickup

5) Delivery of the order to the end user's address

Aspect 5: Roles and Permissions:

1) Administrator:

-   -   a. User management (Add users Administrators, Customer service)    -   b. Disable/Enable access accounts on the platform.    -   c. Revision and validation of documentation for restaurants and        delivery partners.    -   d. Communications Management (Restaurants, delivery staff or end        user, customer service)    -   e. General data configuration on the platform for the Delivery        Optimization algorithm.    -   f. Reports: costs, billing, total orders, most requested meals,        restaurants etc.

2) Restaurant:

-   -   a. Register on the platform    -   b. Approval/Rejection for the onboarding process    -   c. Profile data configuration    -   d. Creation of the food catalog    -   e. Acceptance/Rejection of Orders    -   f. Communications Management

3) Delivery Partners

-   -   a. Register on the platform    -   b. Approval/Rejection for the onboarding process    -   c. Profile data configuration    -   d. Creation of the food catalog    -   e. Acceptance/Rejection of pickup Orders    -   f. Communications Management

4) End User:

-   -   a. Register on the platform    -   b. Advanced search for foods, restaurants, diets, ingredients,        etc.    -   c. Creation and confirmation of the order.    -   d. Order status tracking    -   e. Receipt of the order and qualification of the service    -   f. Communications Management

Aspect 6: Platform Components:

-   -   1) Mobile Application: The mobile application briefly describes        the utility and value of the platform. Will be used by end        users, delivery partners and restaurants for order tracking. The        end users will be able to create multi-order orders, while the        restaurant and the delivery partners will confirm through the        platform if they accept the order.    -   2) Optimization Algorithm: It will be an internal service of the        platform that can be consumed, receiving certain parameters to        return the optimization results in the delivery process.    -   3) Back-office web (out of scope for phase 1): The back-office        will be used by “Delivery Optimization” administrators to manage        users, view their account details (user data, orders placed,        amounts, etc.).    -   4) The back-office will also create and manage the restaurant's        food catalogs (images, ingredients, preparation times, etc.)    -   5) Website landing page (out of scope for phase 1): Landing page        which describes the utility and value of the app and provides a        link to download it to mobile devices

Aspect 7: Operations Enabled for Users:

1. Access the landing page:

-   -   a. It shows the utility and benefits that the use of the        platform brings to the user.    -   b. It will be automatically visible the first time a user enters        the platform. (Previous to login/registration screen).    -   c. Access to User Registration

2. Access to the Home page of the site once registered (Logged on user)

-   -   a. It will display the last orders generated, types of meals of        preference, promotions, restaurants, etc.    -   b. Registered users will have access to the platform

3. Advanced food search

-   -   a. Users can search for restaurants, types of food by types of        ingredients, types of diet, etc.

4. View my orders

-   -   a. The end user will be able to view the total number of orders        placed on the platform. As well as the frequent places.

5. View Favorites

-   -   a. The end user can view the restaurants and meals saved as        favorites for future use.

6. Create an order with multiple orders

-   -   a. You can generate an order with several orders (meals from one        or different restaurants)

7. Order status tracking through geolocation

-   -   a. Visualization status of the order, as well as the geolocation        where the order is located on the map.

8. Profile data configuration

-   -   a. Users will be able to update their profile data, such as        delivery addresses, payment methods, etc.

9. Split payments

-   -   a. Before confirming the order, the end user can decide if the        payment is divided among other users who have been invited to        participate in the order request.

10. Communications

-   -   a. Sending messages between the end user and the delivery man        through the platform or WhatsApp.    -   b. Contact the support of the platform in case of starting a        claim.

11. Visualization of FAQs

-   -   a. Users can access the FAQ section.

Aspect 8: Operations enabled for the Administrators:

1) Create other users Administrators

2) Display a list of registered users.

-   -   b. Access to list of registered users, profile data, email, name        and contact information.    -   c. View and approve pending user registration.    -   d. View a list of history with user transactions.

3) Approve/Reject Restaurants on the platform

4) Set parameters required for the optimization algorithm

-   -   a) Standard tolerance time for the entire delivery process    -   b) Quantity of orders per delivery for optimal food delivery    -   c) Incentives for delivery partners and restaurants based on the        service provided.

5) Access to dashboard section with reports

-   -   a) Billing report.    -   b) Report on the number of users for each profile.    -   c) Transaction history report.    -   d) Report with the detail of the Restaurant's fees.    -   e) Report of transactions distinguished by type/amount/period of        time.    -   f) Report of most requested types of meals.

6) Communications:

-   -   a) Messaging from the platform with the restaurants, Call        Center.

Aspect 9: Operations enabled for Restaurants:

1) Access to the landing page:

-   -   a) Describes the main objective of the platform and benefits.

2) Access to the registration process:

-   -   a) Access to the onboarding process once the documents have been        uploaded    -   b) Waiting for approval/rejection from the platform

3) Access the home page (Once the registration process has beenapproved)

4) Creation of the Catalogue of meals and details of the restaurant:

-   -   a) Loading of dishes    -   b) Images    -   c) Ingredient    -   d) Preparation time    -   e) Maximum conservation time    -   f) Opening and closing hours    -   g) Delay time during peak hours

5) Acceptance/Rejection of an Order

6) Access to performance dashboard

-   -   a) Display metrics and indicators of the orders placed.    -   b) Visualize the amount of your sales.    -   c) Visualize an accumulation of monthly and annual orders.    -   d) Visualize the score that the end user qualifies to the        restaurant.    -   e) View a history of transactions.

7) Creation of promotions

8) Visualize geolocation of the delivery partner on the map

9) Communications with the platform in case of delays.

Aspect 10: Operations enabled for Delivery partners:

1) Access to the landing page:

-   -   a) Describes the main objective of the platform and benefits.

2) Access to the registration process:

-   -   a) Access to the onboarding process once the documents have been        uploaded    -   b) Waiting for approval/rejection from the platform

3) Access the home page (Once the registration process has beenapproved)

4) Acceptance/Rejection of an Order

5) Display position and route on the map points for pickup

-   -   a) Display departure times to the restaurant.    -   b) Visualize arrival times for the collection of the order.    -   c) Visualize the restaurants to pick up.    -   d) Visualize address of the end user for the delivery of the        order.

6) Visualize position and route on the map for the pick-up and deliveryto the end user.

7) Communications with the platform in case of delays.

Aspect 11: Common operations to user profiles:

1) Registration

-   -   a) Select “Register” on the platform, entering your name,        username, password and profile type (End User, Restaurant or        Dealer). Restaurants and Delivery Partners must complete the        document validation process.    -   b) The user can register via the social network or with an email        account.    -   c) Once the registration process is completed the user will        receive a welcome email.

2. Login and Logout

-   -   a) A user enters his email and password to log in    -   b) A user can log out at any time, as well as log out        automatically after a certain amount of time of inactivity for        security reasons.

3. Modify your profile data and password

-   -   a) Users can change their password, main account email and        contact details.    -   b) To make any of these changes, the Investor must re-confirm        their identity using their current password.

4. Recovering your password if you have forgotten it

-   -   a) A user can retrieve their password by entering their account        email. If the email exists in the user base, the user will        receive an email with a one-time link that will allow them to        create a new password.

The following is claimed:
 1. A method for executing a multi-restaurantorder, the method comprising: receiving the multi-restaurant order, by adelivery organizer from a software interface, wherein the deliveryorganizer is a software application executing on a computer, themulti-restaurant order comprising a plurality of order items associatedwith a plurality of restaurants from at least one customer; retrieving,by the delivery organizer, the following information associated with afirst order item, of the plurality of order items, the first order itembeing associated with a first restaurant: a first preparation timeinformation, and a first order temperature information; retrieving, bythe delivery organizer, the following information associated with asecond order item, of the plurality of order items, the second orderitem being associated with a second restaurant: a second preparationtime information, and a second order temperature information; schedulingpickup times, by the delivery organizer, for at least one deliveryprovider to pick up the first order item and the second order item basedon the following: geolocation data of the first restaurant and thesecond restaurant, comparing a target temperature of at least one of thefirst order item and the second order item with at least one of thefollowing: the first order temperature information, and the second ordertemperature information, and a target delivery time for themulti-restaurant order; scheduling, based on order data, a first time tobegin preparation of the first order item and a second time to beginpreparation of the second order item; transmitting, by the deliveryorganizer, the scheduled first time to begin preparation to the firstrestaurant; transmitting, by the delivery organizer, the scheduledsecond time to begin preparation to the second restaurant; transmitting,by the delivery organizer, the pickup times to the at least one deliveryprovider; monitoring, by the delivery organizer, preparation timesassociated with the first order item and the second order item at theirrespective restaurants to detect one or more delays; and transmitting,by the delivery organizer, based on the monitoring, a notification toone or more delivery providers to adjust one or more of the pickuptimes.
 2. The method of claim 1, wherein transmitting the pickup timesto the at least one delivery provider comprises transmitting the pickuptimes to a plurality of delivery drivers.
 3. The method of claim 1,further comprising assigning at least one additional delivery providerin order to deliver the first order item and the second order itemwithin the target delivery time.
 4. The method of claim 1, furthercomprising assigning at least one prerequisite item relating to themulti-restaurant order, the at least one prerequisite item comprising atleast one of the following: at least one thermal container; at least onechafing apparatus; and at least one cooler.
 5. The method of claim 1,wherein receiving the multi-restaurant order further comprises receivingat least one of the following: at least one delivery address; paymentinformation of the at least one customer; contact information of the atleast one customer; the target delivery time; and desired serviceoptions.
 6. The method of claim 1, further comprising receiving acompletion indicator upon a completed delivery from the at least onedelivery provider to a customer of the multi-restaurant order.
 7. Themethod of claim 6, further comprising transmitting payment from thecustomer to at least one of the following based on the completionindicator: the first restaurant; the second restaurant; and the at leastone delivery provider.
 8. The method of claim 1, further comprising:receiving an indication from the first restaurant as to a delay in thefirst preparation time associated with the first order item.
 9. Themethod of claim 1, further comprising: recalculating and adjusting thesecond time to begin preparation of the second order item.
 10. Themethod of claim 1, further comprising at least one of the following:modifying, upon a modification request of the first restaurant, thefirst preparation time information associated with preparing the firstorder item; and modifying, upon a modification request of the secondrestaurant, the second preparation time information associated withpreparing the second order item.
 11. A multi-restaurant order executionsystem comprising: a memory storage; and a processing unit coupled tothe memory storage, the processing unit being configured to perform thefollowing: receive a multi-restaurant order, by a delivery organizerfrom a software interface, wherein the delivery organizer is a softwareapplication executing on a computer, the multi-restaurant ordercomprising a plurality of order items associated with a plurality ofrestaurants from at least one customer, retrieve, by the deliveryorganizer, the following information associated with a first order item,of the plurality of order items, the first order item being associatedwith a first restaurant: a first preparation time information, and afirst order temperature information, retrieve, by the deliveryorganizer, the following information associated with a second orderitem, of the plurality of order items, the second order item beingassociated with a second restaurant: a second preparation timeinformation, and a second order temperature information, schedule pickuptimes, by the delivery organizer, for at least one delivery provider topick up the first order item and the second order item based on thefollowing: geolocation data of the first restaurant and the secondrestaurant, a comparison of a target temperature of at least one of thefirst order item and the second order item with at least one of thefollowing: the first order temperature information, and the second ordertemperature information, and a target delivery time for themulti-restaurant order, schedule, based on order data, a first time tobegin preparation of the first order item and a second time to beginpreparation of the second order item, transmit, by the deliveryorganizer, the scheduled first time to begin preparation to the firstrestaurant, transmit, by the delivery organizer, the scheduled secondtime to begin preparation to the second restaurant, transmit, by thedelivery organizer, the pickup times to the at least one deliveryprovider, monitor, by the delivery organizer, preparation timesassociated with the first order item and the second order item at theirrespective restaurants to detect one or more delays, and transmit, bythe delivery organizer, a notification to one or more delivery providersto adjust one or more of the pickup times.
 12. The system of claim 11,wherein the one or more delivery providers comprises at least one of thefollowing: a robot; a drone; and a driverless vehicle.
 13. The system ofclaim 11, wherein the first preparation time information comprises atime associated with preparing the first order item associated with thefirst restaurant.
 14. The system of claim 11, further configured toassign at least one prerequisite item relating to the multi-restaurantorder, the at least one prerequisite item comprising at least one of thefollowing: at least one thermal container; at least one chafingapparatus; and at least one cooler.
 15. The system of claim 11, whereinreceiving the multi-restaurant order further comprises receiving atleast one of the following: at least one delivery address; paymentinformation of the at least one customer; contact information of the atleast one customer; and desired service options.
 16. The system of claim11, further configured to receive a completion indicator upon acompleted delivery from the one or more delivery providers to the atleast one customer of the multi-restaurant order.
 17. The system ofclaim 16, further configured to transmit payment from the at least onecustomer to at least one of the following based on the completionindicator: the first restaurant; the second restaurant; and the at leastone delivery provider.
 18. The system of claim 11, further configured toreceive an indication from the first restaurant as to a delay in thefirst time to begin preparation of the first order item.
 19. The systemof claim 11, further configured to recalculate and adjust the secondtime to begin preparation of the second order item.
 20. A non-transitorycomputer readable medium comprising a set of instructions which, whenexecuted by a computer, perform a method, the method comprising:receiving a multi-restaurant order, by a delivery organizer from asoftware interface, wherein the delivery organizer is a softwareapplication executing on the computer, the multi-restaurant ordercomprising a plurality of order items associated with a plurality ofrestaurants from at least one customer; retrieving, by the deliveryorganizer, the following information associated with a first order item,of the plurality of order items, the first order item being associatedwith a first restaurant: a first preparation time information, and afirst order temperature information; retrieving, by the deliveryorganizer, the following information associated with a second orderitem, of the plurality of order items, the second order item beingassociated with a second restaurant: a second preparation timeinformation, and a second order temperature information; schedulingpickup times, by the delivery organizer, for at least one deliveryprovider to pick up the first order item and the second order item basedon the following: geolocation data of the first restaurant and thesecond restaurant, comparing a target temperature of at least one of thefirst order item and the second order item with at least one of thefollowing: the first order temperature information, and the second ordertemperature information, and a target delivery time for themulti-restaurant order; scheduling, based on order data, a first time tobegin preparation of the first order item and a second time to beginpreparation of the second order item; transmitting, by the deliveryorganizer, the scheduled first time to begin preparation to the firstrestaurant; transmitting, by the delivery organizer, the scheduledsecond time to begin preparation to the second restaurant; transmitting,by the delivery organizer, the pickup times to the at least one deliveryprovider; monitoring, by the delivery organizer, preparation timesassociated with the first order item and the second order item at theirrespective restaurants to detect one or more delays; and transmitting,by the delivery organizer, based on the monitoring, a notification toone or more delivery providers to adjust one or more of the pickuptimes.